Re: standby promotion can create unreadable WAL

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: standby promotion can create unreadable WAL
Date: 2022-08-28 04:46:21
Message-ID: CAFiTN-uACzpN1O-N__AMhO1bem_8bshuf7J8NYp8Y17CdcG8Yg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 26, 2022 at 7:53 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Fri, Aug 26, 2022 at 10:06 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > There's a small typo in the comment: "When find that". I suppose that
> > was meant to be "When we find that". You end that para with "and thus
> > we should not do this", but that sounds like it wouldn't matter if we
> > did. Maybe "and thus doing this would be wrong, so skip it." or
> > something like that. (Perhaps be even more specific and say "if we did
> > this, we would later create an overwrite record in the wrong place,
> > breaking everything")
>
> I think that saying that someone should not do something implies
> pretty clearly that it would be bad if they did. But I have no problem
> with your more specific language, and as a general rule, it's good to
> be specific, so let's use that.
>
> v2 attached.

The patch LGTM, this patch will apply on master and v15. PFA patch
for back branches.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

Attachment Content-Type Size
fix-contrecord-condition-v2_v14_v96.patch application/octet-stream 1.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-08-28 07:23:08 Re: [PATCH] Add native windows on arm64 support
Previous Message Nathan Bossart 2022-08-28 03:58:39 Re: use ARM intrinsics in pg_lfind32() where available