diff options
| author | Stephen Frost <sfrost@snowman.net> | 2017-03-22 23:44:58 -0400 |
|---|---|---|
| committer | Stephen Frost <sfrost@snowman.net> | 2017-03-22 23:44:58 -0400 |
| commit | 017e4f2588a7fc6f2d1fbb6fff8afa1ff6e31f2b (patch) | |
| tree | 6684c386c0d35fd059018e56a15b1ebfa3481879 /src/backend/commands/subscriptioncmds.c | |
| parent | cbf7ed51b8c0c3e506b91765769f76d5c2e1e9ac (diff) | |
| download | postgresql-017e4f2588a7fc6f2d1fbb6fff8afa1ff6e31f2b.tar.gz postgresql-017e4f2588a7fc6f2d1fbb6fff8afa1ff6e31f2b.zip | |
Expose waitforarchive option through pg_stop_backup()
Internally, we have supported the option to either wait for all of the
WAL associated with a backup to be archived, or to return immediately.
This option is useful to users of pg_stop_backup() as well, when they
are reading the stop backup record position and checking that the WAL
they need has been archived independently.
This patch adds an additional, optional, argument to pg_stop_backup()
which allows the user to indicate if they wish to wait for the WAL to be
archived or not. The default matches current behavior, which is to
wait.
Author: David Steele, with some minor changes, doc updates by me.
Reviewed by: Takayuki Tsunakawa, Fujii Masao
Discussion: https://postgr.es/m/758e3fd1-45b4-5e28-75cd-e9e7f93a4c02@pgmasters.net
Diffstat (limited to 'src/backend/commands/subscriptioncmds.c')
0 files changed, 0 insertions, 0 deletions