Re: pgsql: pg_upgrade: simplify code layout in a few places

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: pg_upgrade: simplify code layout in a few places
Date: 2018-01-06 01:39:46
Message-ID: 20249.1515202786@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-01-05 18:57:55 -0500, Bruce Momjian wrote:
>> On Fri, Jan 5, 2018 at 03:51:15PM -0800, Andres Freund wrote:
>>> Also, leaving translatability aside, why was *any* of this backpatched?

>> Tom has preferred that I backpatch all safe patches so we keep that code
>> consistent so we can backpatch other things more easily.

> I've a hard time believing this. Tom?

I've been known to back-patch stuff just to keep branches consistent,
but it's always a judgement call. In this case I wouldn't have done it
(even if the patch were a good idea in HEAD) because it would cause
churn in translatable messages in the back branches. Also, the case
for cosmetic back-patching is only strong when a particular file is
already pretty similar across all branches, and I'm not sure that
holds for pg_upgrade.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2018-01-06 02:10:52 Re: pgsql: pg_upgrade: simplify code layout in a few places
Previous Message Tom Lane 2018-01-06 01:33:31 pgsql: Remove return values of ConditionVariableSignal/Broadcast.

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2018-01-06 02:10:52 Re: pgsql: pg_upgrade: simplify code layout in a few places
Previous Message Ryan Murphy 2018-01-06 00:58:09 Re: January CommitFest is underway!