Skip to content

Commit b804c18

Browse files
committed
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
1 parent d08c44f commit b804c18

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

doc/src/sgml/func.sgml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19835,6 +19835,8 @@ SELECT set_config('log_statement_stats', 'off', false);
1983519835
The functions shown in <xref
1983619836
linkend="functions-admin-backup-table"/> assist in making on-line backups.
1983719837
These functions cannot be executed during recovery (except
19838+
non-exclusive <function>pg_start_backup</function>,
19839+
non-exclusive <function>pg_stop_backup</function>,
1983819840
<function>pg_is_in_backup</function>, <function>pg_backup_start_time</function>
1983919841
and <function>pg_wal_lsn_diff</function>).
1984019842
</para>

0 commit comments

Comments
 (0)