Re: Add exclusive backup deprecation notes to documentation

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>, David Steele <david(at)pgmasters(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Martín Marqués <martin(at)2ndquadrant(dot)com>
Subject: Re: Add exclusive backup deprecation notes to documentation
Date: 2019-03-29 12:56:51
Message-ID: 875da582-ba7a-bd04-9ba0-b7be422c26b6@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-03-29 13:54, Magnus Hagander wrote:
> Is the changes to the messages going to cause issues or weirdness for
> translators? That would be a reason not to backpatch it. Without that,
> I'm leaning towards backpatching it.

Note that the messages refer to recovery.signal, so a backpatch would
have to rephrase the message.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-03-29 13:05:05 Re: fsync error handling in pg_receivewal, pg_recvlogical
Previous Message Magnus Hagander 2019-03-29 12:54:40 Re: Add exclusive backup deprecation notes to documentation