Re: PATCH: Make pg_stop_backup() archive wait optional

Jim Nasby <jim.nasby@bluetreble.com>

From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: David Steele <david@pgmasters.net>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-03-01T22:11:49Z
Lists: pgsql-hackers
On 2/27/17 6:25 PM, David Steele wrote:
> The purpose of this patch is to make waiting for archive optional, with
> the default being the current behavior, i.e., to wait for all WAL to be
> archived.  This functionality is already used internally by
> pg_basebackup, so the only real change is to expose it through the
> pg_stop_backup() function.

Do the docs mention anywhere how to monitor WAL archiving to know if 
you've got all the necessary WAL? Perhaps a function to do that would be 
worth adding.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)


Commits

  1. Expose waitforarchive option through pg_stop_backup()

  2. Mark pg_start_backup and pg_stop_backup as parallel-restricted.