Re: Commit/abort WAL records with dropped rels missing XLR_SPECIAL_REL_UPDATE - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Commit/abort WAL records with dropped rels missing XLR_SPECIAL_REL_UPDATE
Date
Msg-id 20200817070017.GE7787@paquier.xyz
Whole thread Raw
In response to Re: Commit/abort WAL records with dropped rels missing XLR_SPECIAL_REL_UPDATE  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Commit/abort WAL records with dropped rels missing XLR_SPECIAL_REL_UPDATE  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Sat, Aug 15, 2020 at 11:05:43AM +0530, Amit Kapila wrote:
> On Fri, Aug 14, 2020 at 2:17 PM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>> It's always been like that, but I am not going backport, for fear of
>> breaking existing applications. If a program reads the WAL, and would
>> actually need to do something with commit records dropping relations,
>> that seems like such a common scenario that the author should've thought
>> about it and handled it even without the flag reminding about it. Fixing
>> it in master ought to be enough.
>
> +1 for doing it in master only. Even if someone comes up with such a
> scenario for back-branches, we can revisit our decision to backport
> this but like you, I also don't see any pressing need to do it now.

+1.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: More tests with USING INDEX replident and dropped indexes
Next
From: Heikki Linnakangas
Date:
Subject: Re: Newline after --progress report