Re: Add exclusive backup deprecation notes to documentation

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

On Wed, Mar 20, 2019 at 04:29:35PM +0400, David Steele wrote:
> Please note that there have been objections to the patch later in this
> thread by Peter and Robert. I'm not very interested in watering down the
> documentation changes as Peter suggests, but I think at the very least we
> should commit the added hints in the error message. For many users this
> error will be their first point of contact with the backup_label
> issue/behavior.

The updates of the log message do not imply anything negative as I
read them as they mention to not remove the backup_label file. So
while we don't have an agreement about the docs, the log messages may
be able to be committed? Peter? Robert?

"will result in a corruptED cluster" is more correct?

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2019-03-20 13:28:34 Re: Re: query logging of prepared statements
Previous Message Michael Paquier 2019-03-20 12:54:51 Re: Offline enabling/disabling of data checksums