From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: base backup client as auxiliary backend process
Date: Wed, 11 Sep 2019 19:15:24 -0300
Message-ID: <20190911221524.GA16563@alvherre.pgsql> (raw)
In-Reply-To: <62e860f2-ae4b-67a1-b65d-04c3d1bf6aff@2ndquadrant.com>
On 2019-Aug-30, Peter Eisentraut wrote:
> Attached is an updated patch for this. I have changed the initdb option
> name per suggestion. The WAL receiver is now started concurrently with
> the base backup. There is progress reporting (ps display), fsyncing.
> Configuration files are not copied anymore. There is a simple test
> suite. Tablespace support is still missing, but it would be
> straightforward.
This is an amazing feature. How come we don't have people cramming to
review this?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: alvherre@2ndquadrant.com, peter.eisentraut@2ndquadrant.com
Subject: Re: base backup client as auxiliary backend process
In-Reply-To: <20190911221524.GA16563@alvherre.pgsql>
* 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