Re: Use of term hostaddrs for multiple hostaddr values - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Use of term hostaddrs for multiple hostaddr values
Date
Msg-id CABUevExxHqFEsxnzEJ+UuvBcUi=prU0dhKH0xwrEYD25rQPS7w@mail.gmail.com
Whole thread Raw
In response to Re: Use of term hostaddrs for multiple hostaddr values  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Use of term hostaddrs for multiple hostaddr values
List pgsql-hackers


On Sun, Jan 21, 2018 at 12:45 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
On 1/20/18 17:39, Michael Paquier wrote:
> On Sat, Jan 20, 2018 at 08:30:43PM +0200, Magnus Hagander wrote:
>> On Tue, Jan 9, 2018 at 5:34 AM, Michael Paquier <michael.paquier@gmail.com>
>> wrote:
>> These are both clear bugs, and the docs one should definitely be both
>> applied and backpatched.
>>
>> How much do we care about the error message when it comes to backpatching?
>> Maybe we should leave that one to 11 only, to avoid breaking that, as the
>> way it's written it's actually less wrong there.
>>
>> Thoughts?
>
> Thanks for your input!
>
> Applying the error message portion only on HEAD is a good plan, there is
> no point to make the life of translaters unnecessary painful.

I would backpatch both.  The updated error message is arguably easier to
translate.

Fair enough. And since you do the translation merging at least, I'll go with that.

Thus, applied and backpatched to 10.

Thanks! 

--

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Supporting huge pages on Windows
Next
From: Michael Paquier
Date:
Subject: Re: Use of term hostaddrs for multiple hostaddr values