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 12:25:42 +0900
Message-ID: <20181129032542.GL626@paquier.xyz> (raw)
In-Reply-To: <20181129023957.GU3415@tamriel.snowman.net>
References: <154340283171.1324.10549444217937216132@wrigleys.postgresql.org>
<20181129022347.GH626@paquier.xyz>
<20181129023957.GU3415@tamriel.snowman.net>
On Wed, Nov 28, 2018 at 09:39:58PM -0500, Stephen Frost wrote:
> Having discussed this quite a bit lately with David Steele and Magnus,
> it's pretty clear that we need to completely rip out how this works
> today and rewrite it based around an extension model where a background
> worker can start up and essentially take the place of the archiver
> process, with flexibility to jump forward through the WAL stream,
> communicate clearly with other processes, handle failure to do so
> gracefully based on the specific cases, etc.
Hm. When an instance state is in PM_SHUTDOWN_2, the postmaster
explicitely waits for the WAL senders and the archiver to shut down. So
I think that you would need more control regarding the timing a bgworker
should be shut down first to be completely correct.
--
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: <20181129032542.GL626@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