From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: David Steele <david@pgmasters.net>
To: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: PATCH: Make pg_stop_backup() archive wait optional
Date: Wed, 1 Mar 2017 16:11:49 -0600
Message-ID: <bc0bf94b-5975-4879-9e75-2a57688348c5@BlueTreble.com> (raw)
In-Reply-To: <758e3fd1-45b4-5e28-75cd-e9e7f93a4c02@pgmasters.net>
References: <758e3fd1-45b4-5e28-75cd-e9e7f93a4c02@pgmasters.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, david@pgmasters.net
Subject: Re: PATCH: Make pg_stop_backup() archive wait optional
In-Reply-To: <bc0bf94b-5975-4879-9e75-2a57688348c5@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox