pgsql: Fix documentation of pg_start_backup and pg_stop_backup function

From: Fujii Masao <fujii(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix documentation of pg_start_backup and pg_stop_backup function
Date: 2019-04-22 17:45:45
Message-ID: E1hId0j-0003ac-3h@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b804c1837b55722369d30be707738c098a75cd7a

Modified Files
--------------
doc/src/sgml/func.sgml | 2 ++
1 file changed, 2 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Laurenz Albe 2019-04-22 19:37:25 Re: pgsql: Allow insert and update tuple routing and COPY for foreign table
Previous Message Fujii Masao 2019-04-22 17:45:30 pgsql: Fix documentation of pg_start_backup and pg_stop_backup function