Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Date
Msg-id 417711.1637940660@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Thu, Nov 25, 2021 at 06:19:03PM -0800, SATYANARAYANA NARLAPURAM wrote:
>> If we are keeping it then why not make it better?

> Well, non-exclusive backups are better by design in many aspects, so I
> don't quite see the point in spending time on something that has more
> limitations than what's already in place.

IMO the main reason for keeping it is backwards compatibility for users
who have a satisfactory backup arrangement using it.  That same argument
implies that we shouldn't change how it works (at least, not very much).

            regards, tom lane



pgsql-hackers by date:

Previous
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: Optionally automatically disable logical replication subscriptions on error
Next
From: Parth Shah
Date:
Subject: Contributing