Re: pgsql: Remove references to Majordomo

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Remove references to Majordomo
Date: 2019-01-19 00:04:20
Message-ID: 20190119000420.GA2660@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, Jan 18, 2019 at 10:02:47AM -0500, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> You are right, we definitely should. I'll go ahead and fix that. I can't
>> quite make up my mind on if it's a good idea to backpatch that though --
>> it's certainly safe enough to do, but it might cause issues for translators?
>
> Yeah, weak -1 for back-patching. We don't usually like to thrash
> translatable messages in the back branches.

Yes, I think that it is better to not bother about back-branches and
just do that on HEAD.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2019-01-19 00:08:27 Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Previous Message Tom Lane 2019-01-18 20:34:30 Re: pgsql: Restrict the use of temporary namespace in two-phase transaction

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-01-19 00:06:58 Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages)
Previous Message Alexander Korotkov 2019-01-18 23:54:52 Re: jsonpath