| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Use of term hostaddrs for multiple hostaddr values |
| Date: | 2018-01-20 22:45:25 |
| Message-ID: | 00089180-a006-c4b5-ee99-b766d13df14a@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(dot)paquier(at)gmail(dot)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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-01-20 22:47:20 | Re: PATCH: Configurable file mode mask |
| Previous Message | Michael Paquier | 2018-01-20 22:39:21 | Re: Use of term hostaddrs for multiple hostaddr values |