pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Noah Misch <noah@leadboat.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17928: Standby fails to decode WAL on termination of primary
Date: Sat, 12 Aug 2023 09:20:32 +0900
Message-ID: <ZNbQUDcZK0ELn1o9@paquier.xyz> (raw)
In-Reply-To: <CA+hUKGLEF7-bK3=KFYfaDMOh8wy2XdMOncbUrn=JrhmjX0_vPQ@mail.gmail.com>
References: <72bd036d-4f2a-8d50-b56e-6b1e3b9ba0a9@gmail.com>
	<CA+hUKG+t8gfYBS2TRMW6rHaWUBEC1Cy+p-0pgPBx8ag8TBeoKw@mail.gmail.com>
	<20230710200012.GB3476234@rfd.leadboat.com>
	<20230711.155414.939136339819647605.horikyota.ntt@gmail.com>
	<20230717004905.GE3826297@rfd.leadboat.com>
	<ZNSVlR/v8gTDIMsU@paquier.xyz>
	<20230811025808.GA2261232@rfd.leadboat.com>
	<ZNXQWvnmt1Fpt6vu@paquier.xyz>
	<20230811140008.GB2261449@rfd.leadboat.com>
	<CA+hUKGLEF7-bK3=KFYfaDMOh8wy2XdMOncbUrn=JrhmjX0_vPQ@mail.gmail.com>

On Sat, Aug 12, 2023 at 11:56:45AM +1200, Thomas Munro wrote:
> On Sat, Aug 12, 2023 at 2:00 AM Noah Misch <noah@leadboat.com> wrote:
>> On Fri, Aug 11, 2023 at 03:08:26PM +0900, Michael Paquier wrote:
>> I recall earlier messages theorizing that it was just harder to hit in v14, so
>> I'm disinclined to stop at v15.  I think the main choice is whether to stop at
>> v11 (normal choice) or v12 (worry about breaking the last v11 point release).
>> I don't have a strong opinion between those.

Okay.  I wouldn't be inclined to patch v11 for that, FWIW, as this
code path is touched by recovery and more.  At least it does not seem 
worth taking any risk compared to the potential gain.

> Thanks for working on this.
> 
> I wonder if we need a more explicit way to construct pages with the
> right bits to reach interesting test cases and get full enough
> coverage...  (Cf throwing SQL at the WAL to see if it sticks.)

You mean SQL functions that write an arbitrary set of bytes at a given
LSN, to trigger some expected behavior on a follow-up crash recovery?
--
Michael

Attachments:

  [application/pgp-signature] signature.asc (832B, ../ZNbQUDcZK0ELn1o9@paquier.xyz/2-signature.asc)
  download

view thread (86+ messages)  latest in thread

Message-ID: <ZNbQUDcZK0ELn1o9@paquier.xyz>
Permalink:  ../ZNbQUDcZK0ELn1o9@paquier.xyz/
Also on:    postgresql.org/message-id/ZNbQUDcZK0ELn1o9@paquier.xyz

 · 

reply

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-bugs@postgresql.org
  Cc: michael@paquier.xyz, thomas.munro@gmail.com, noah@leadboat.com, horikyota.ntt@gmail.com, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #17928: Standby fails to decode WAL on termination of primary
  In-Reply-To: <ZNbQUDcZK0ELn1o9@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