Re: Improve behavior of concurrent TRUNCATE

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve behavior of concurrent TRUNCATE
Date: 2018-08-10 20:53:58
Message-ID: 20180810205358.GC22736@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-08-10 20:57:57 Re: logical decoding / rewrite map vs. maxAllocatedDescs
Previous Message Tom Lane 2018-08-10 20:50:55 Re: NLS handling fixes.