Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitcee3cfd

Browse files
committed
Fix documentation of pg_start_backup and pg_stop_backup functions.
This commit adds the description that "non-exclusive" pg_start_backupand pg_stop_backup can be executed even during recovery. Previouslyit was wrongly documented that those functions are not allowed to beexecuted 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 parentab01aa8 commitcee3cfd

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
@@ -18687,6 +18687,8 @@ SELECT set_config('log_statement_stats', 'off', false);
1868718687
The functions shown in <xref
1868818688
linkend="functions-admin-backup-table"/> assist in making on-line backups.
1868918689
These functions cannot be executed during recovery (except
18690+
non-exclusive <function>pg_start_backup</function>,
18691+
non-exclusive <function>pg_stop_backup</function>,
1869018692
<function>pg_is_in_backup</function>, <function>pg_backup_start_time</function>
1869118693
and <function>pg_wal_lsn_diff</function>).
1869218694
</para>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp