Re: BUG #17928: Standby fails to decode WAL on termination of primary - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17928: Standby fails to decode WAL on termination of primary
Date
Msg-id ZQlvihvHo5JspVpV@paquier.xyz
Whole thread Raw
In response to Re: BUG #17928: Standby fails to decode WAL on termination of primary  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: BUG #17928: Standby fails to decode WAL on termination of primary
List pgsql-bugs
On Tue, Sep 19, 2023 at 09:25:34PM +1200, Thomas Munro wrote:
> The problem was that the Perl functions advance_XXX() would sometimes
> see an "unflushed" insert position caused by hint records and other
> incidental stuff, and then we'd write our contrived header at a
> disconnected location after a bunch of (unwritten) zeroes.  The
> solution in this version is to start each test with
> emit_message($node, 0), which flushes a small record.

Makes sense.  Does this also address the other issue you've noticed on
v12 when ICU is enabled (the one with the initial LSN changed after
initdb)?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #17928: Standby fails to decode WAL on termination of primary
Next
From: Thomas Munro
Date:
Subject: Re: BUG #17928: Standby fails to decode WAL on termination of primary