From: Noah Misch <noah@leadboat.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: last_archived_wal is not necessary the latest WAL file (was Re: pgsql: Add test case for an archive recovery corner case.)
Date: Wed, 29 Jun 2022 22:03:10 -0700
Message-ID: <20220630050310.GB2257984@rfd.leadboat.com> (raw)
In-Reply-To: <YrmHKCOBA1tR9PFy@paquier.xyz>
References: <E1nJXkI-0004VV-C3@gemulon.postgresql.org>
<2842251.1644849700@sss.pgh.pa.us>
<8f15e602-337e-fbb2-4b2e-e83a01ef9088@iki.fi>
<831b6ab9-45d6-7ab0-ea9c-6efd4383afb8@iki.fi>
<3186114.1644960507@sss.pgh.pa.us>
<40de25aa-2e20-08ad-e014-edb731594a74@iki.fi>
<20220627070457.GA2176699@rfd.leadboat.com>
<YrmHKCOBA1tR9PFy@paquier.xyz>
On Mon, Jun 27, 2022 at 07:32:08PM +0900, Michael Paquier wrote:
> On Mon, Jun 27, 2022 at 12:04:57AM -0700, Noah Misch wrote:
> > One can adapt the test to the server behavior by having the test wait for the
> > archiver to start, as attached. This is sufficient to make check-world pass
> > with the above sleep in place. I think we should also modify the PostgresNode
> > archive_command to log a message. That lack of logging was a obstacle
> > upthread (as seen in commit 3279cef) and again here.
>
> ? qq{copy "%p" "$path\\\\%f"}
> - : qq{cp "%p" "$path/%f"};
> + : qq{echo >&2 "ARCHIVE_COMMAND %p"; cp "%p" "$path/%f"};
>
> This is a bit inelegant. Perhaps it would be better through a perl
> wrapper like cp_history_files?
I see it the other way. Replacing a 49-character compound command with a
wrapper script would gain no particular advantage, and it would give readers
of the test code one more file to open and understand.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: noah@leadboat.com, michael@paquier.xyz, hlinnaka@iki.fi, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: last_archived_wal is not necessary the latest WAL file (was Re: pgsql: Add test case for an archive recovery corner case.)
In-Reply-To: <20220630050310.GB2257984@rfd.leadboat.com>
References: <E1nJXkI-0004VV-C3@gemulon.postgresql.org> <2842251.1644849700@sss.pgh.pa.us> <8f15e602-337e-fbb2-4b2e-e83a01ef9088@iki.fi> <831b6ab9-45d6-7ab0-ea9c-6efd4383afb8@iki.fi> <3186114.1644960507@sss.pgh.pa.us> <40de25aa-2e20-08ad-e014-edb731594a74@iki.fi> <20220627070457.GA2176699@rfd.leadboat.com> <YrmHKCOBA1tR9PFy@paquier.xyz> <20220630050310.GB2257984@rfd.leadboat.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