Re: Improve behavior of concurrent TRUNCATE - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Improve behavior of concurrent TRUNCATE
Date
Msg-id 20180810205358.GC22736@paquier.xyz
Whole thread Raw
In response to Re: Improve behavior of concurrent TRUNCATE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Improve behavior of concurrent TRUNCATE
List pgsql-hackers
On Fri, Aug 10, 2018 at 02:03:28PM -0400, Alvaro Herrera wrote:
> On 2018-Aug-06, Michael Paquier wrote:
>> Like cbe24a6, perhaps we would not want to back-patch it?  Based on the
>> past history (and the consensus being reached for the REINDEX case would
>> be to patch only HEAD), I would be actually incline to not back-patch
>> this stuff and qualify that as an improvement.  That's also less work
>> for me at commit :)
>
> I'm not sure I understand your arguments for not back-patching this.

Mainly consistency.  Looking at the git history for such cases we have
not really bothered back-patching fixes and those have been qualified as
improvements.  If we were to close all the holes mentioned in the
original DOS thread a back-patch to v11 could be thought as acceptable?
That's where the REINDEX fix has found its way after all, but that was
way less code churn, and we are post beta 3 for v11...
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: NLS handling fixes.
Next
From: Tomas Vondra
Date:
Subject: Re: logical decoding / rewrite map vs. maxAllocatedDescs