Re: PATCH: Make pg_stop_backup() archive wait optional
David Steele <david@pgmasters.net>
From: David Steele <david@pgmasters.net>
To: pgsql-hackers@postgresql.org
Date: 2017-04-04T16:23:25Z
Lists: pgsql-hackers
On 4/4/17 11:42 AM, Stephen Frost wrote: > * David Steele (david@pgmasters.net) wrote: >> On 3/22/17 4:42 PM, Peter Eisentraut wrote: >>> On 3/22/17 15:14, Stephen Frost wrote: >>>>> -SELECT * FROM pg_stop_backup(false); >>>>> +SELECT * FROM pg_stop_backup(false [, true ]); >>>>> >>>>> I think that it's better to get rid of "[" and "]" from the above because >>>>> IMO this should be the command example that users actually can run. >>>> Using the '[' and ']' are how all of the optional arguments are >>>> specified in the documentation, see things like current_setting() in our >>>> existing documentation: >>> >>> In the synopsis, but not in concrete examples. >> >> Wasn't quite sure what the protocol was in this case, and figured it >> was easier to subtract than to add. > > Forgot to close this out sooner, apologies. > > This has been committed now. Thank you, Stephen! -- -David david@pgmasters.net
Commits
-
Expose waitforarchive option through pg_stop_backup()
- 017e4f2588a7 10.0 landed
-
Mark pg_start_backup and pg_stop_backup as parallel-restricted.
- 9fe3c644a731 10.0 landed