summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFujii Masao2019-04-22 17:41:58 +0000
committerFujii Masao2019-04-22 17:44:25 +0000
commit5241f689995dd2bbd39c26c6fa150ca47e2f3601 (patch)
treef685b6a5a12c89632fd6c33faed17ab0be36d492
parente356005d1c9c17fce5c06e686820605bc82ae2d5 (diff)
Fix documentation of pg_start_backup and pg_stop_backup functions.
This commit adds the description that "non-exclusive" pg_start_backup and pg_stop_backup can be executed even during recovery. Previously it was wrongly documented that those functions are not allowed to be executed during recovery. Back-patch to 9.6 where non-exclusive backup API was added. Discussion: https://postgr.es/m/CAHGQGwEuAYrEX7Yhmf2MCrTK81HDkkg-JqsOUh8zw6+zYC5zzw@mail.gmail.com
-rw-r--r--doc/src/sgml/func.sgml2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index b96049ae325..af5ec0c2e1e 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -17976,6 +17976,8 @@ SELECT set_config('log_statement_stats', 'off', false);
The functions shown in <xref
linkend="functions-admin-backup-table"> assist in making on-line backups.
These functions cannot be executed during recovery (except
+ non-exclusive <function>pg_start_backup</function>,
+ non-exclusive <function>pg_stop_backup</function>,
<function>pg_is_in_backup</function>, <function>pg_backup_start_time</function>
and <function>pg_xlog_location_diff</function>).
</para>