From: Michael Paquier <michael@paquier.xyz>
To: Stephen Frost <sfrost@snowman.net>
Cc: splarv@ya.ru
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Return codes for archive and restore commands
Date: Thu, 29 Nov 2018 14:42:20 +0900
Message-ID: <20181129054220.GM626@paquier.xyz> (raw)
In-Reply-To: <20181129032731.GV3415@tamriel.snowman.net>
References: <154340283171.1324.10549444217937216132@wrigleys.postgresql.org>
<20181129022347.GH626@paquier.xyz>
<20181129023957.GU3415@tamriel.snowman.net>
<20181129032542.GL626@paquier.xyz>
<20181129032731.GV3415@tamriel.snowman.net>
On Wed, Nov 28, 2018 at 10:27:31PM -0500, Stephen Frost wrote:
> Yes, it couldn't be exactly the same as a generic background worker,
> that's a good point. We definitely need to make sure that the
> postmaster waits for the archiver to shut down, as it does for the WAL
> senders.
Just to be clear, please note I don't think that what removing the
archiver code from the core code is a bad idea, quite the contrary
actually. But I doubt that it would be acceptable to rip off this code
without something which has the same properties and guarantees for any
users depending on it. And archive_command is used a lot.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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-docs@postgresql.org
Cc: michael@paquier.xyz, sfrost@snowman.net, splarv@ya.ru, pgsql-docs@lists.postgresql.org
Subject: Re: Return codes for archive and restore commands
In-Reply-To: <20181129054220.GM626@paquier.xyz>
* 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