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)
