From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, David Steele <david(at)pgmasters(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Remove Deprecated Exclusive Backup Mode |
Date: | 2020-07-01 15:30:12 |
Message-ID: | 20200701153012.GC5186@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 1, 2020 at 04:46:59PM +0200, Laurenz Albe wrote:
> On Wed, 2020-07-01 at 08:47 -0400, Stephen Frost wrote:
> > > I remain -1 on removing the exclusive backup API.
> >
> > It's still deprecated and I'm certainly against removing that status
> > until/unless someone actually fixes it (including documentation), and if
> > we're not going to do that then we should remove it.
>
> Well, it doesn't need fixing, since it is working just fine (for certain
> values of "just fine").
>
> I agree with the need to document the problems better.
Agreed, and I don't support the repeated attempts to force things. For
me, the exclusive mode got marked as deprecated because it is "not
optimal", but that doesn't mean it is useless or needs to be removed.
Frankly, I think we should remove deprecated and just mark it as
non-optimal.
I do like the idea of pg_start_backup returning a value that needs to be
supplied to pg_stop_backup.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2020-07-01 15:33:53 | Re: Remove Deprecated Exclusive Backup Mode |
Previous Message | Alvaro Herrera | 2020-07-01 15:14:21 | Re: min_safe_lsn column in pg_replication_slots view |