Fix documentation of pg_start_backup and pg_stop_backup functions.
authorFujii Masao
Mon, 22 Apr 2019 17:41:58 +0000 (02:41 +0900)
committerFujii Masao
Mon, 22 Apr 2019 17:44:06 +0000 (02:44 +0900)
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

doc/src/sgml/func.sgml

index 8fd1288dca9bcaf94ad352a9fe0ff42a2ad3565f..4b79566b3c0b3465ba1fb6a5f9237c70600e11bf 100644 (file)
@@ -18533,6 +18533,8 @@ SELECT set_config('log_statement_stats', 'off', false);
     The functions shown in 
     linkend="functions-admin-backup-table"> assist in making on-line backups.
     These functions cannot be executed during recovery (except
+    non-exclusive pg_start_backup,
+    non-exclusive pg_stop_backup,
     pg_is_in_backuppg_backup_start_time
     and pg_wal_lsn_diff).