From: Michael Paquier <michael@paquier.xyz>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Bossart, Nathan <bossartn@amazon.com>
Cc: David Steele <david@pgmasters.net>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Stephen Frost <sfrost@snowman.net>
Subject: Re: archive modules
Date: Wed, 14 Sep 2022 14:25:30 +0900
Message-ID: <YyFlylmDabc/eEH8@paquier.xyz> (raw)
In-Reply-To: <9366d634-a917-85a9-4991-b2a4859edaf9@enterprisedb.com>
References: <20220202224433.GA1036711@nathanxps13>
<CA+TgmoYJ9pTRdX35E35q=+5zetrpOyBh=QnU532C4zvsL1xWdQ@mail.gmail.com>
<20220203192747.GA1080581@nathanxps13>
<CA+Tgmoa+Sp9w2CAkEJ4MuD2sAjePOmVWiYh1yDvVx4P--4ZbUg@mail.gmail.com>
<20220203211121.GA1081379@nathanxps13>
<CA+TgmoYDiOPrEAwzf4MAp-RPRo4TgU1MHfuDOBz-FupWfDa74A@mail.gmail.com>
<20220203212539.GA1082940@nathanxps13>
<CA+TgmoYE7hSUUMfNwKOzHBQ+x6Ge9ThiDbQHXCZ5ty=fGQf7YA@mail.gmail.com>
<20220203215537.GA1123901@nathanxps13>
<9366d634-a917-85a9-4991-b2a4859edaf9@enterprisedb.com>
On Wed, Sep 14, 2022 at 06:37:38AM +0200, Peter Eisentraut wrote:
> I noticed that this patch has gone around and mostly purged mentions of
> archive_command from the documentation and replaced them with
> archive_library. I don't think this is helpful, since people still use
> archive_command and will want to see what the documentation has to say
> about it. I suggest we rewind that a bit and for example replace things
> like
>
> removed or recycled until they are archived. If WAL archiving cannot keep up
> - with the pace that WAL is generated, or if <varname>archive_command</varname>
> + with the pace that WAL is generated, or if <varname>archive_library</varname>
> fails repeatedly, old WAL files will accumulate in <filename>pg_wal</filename>
>
> with
>
> removed or recycled until they are archived. If WAL archiving cannot keep up
> with the pace that WAL is generated, or if <varname>archive_command</varname>
> with the pace that WAL is generated, or if <varname>archive_command</varname>
> or <varname>archive_library</varname>
> fail repeatedly, old WAL files will accumulate in <filename>pg_wal</filename>
Yep. Some references to archive_library have been changed by 31e121
to do exactly that. There seem to be more spots in need of an
update.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../YyFlylmDabc%2FeEH8@paquier.xyz/2-signature.asc)
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-hackers@postgresql.org
Cc: michael@paquier.xyz, peter.eisentraut@enterprisedb.com, nathandbossart@gmail.com, robertmhaas@gmail.com, bossartn@amazon.com, david@pgmasters.net, masao.fujii@oss.nttdata.com, magnus@hagander.net, sfrost@snowman.net
Subject: Re: archive modules
In-Reply-To: <YyFlylmDabc/eEH8@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