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

From SATYANARAYANA NARLAPURAM
Subject Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Date
Msg-id CAHg+QDekOasWArvmPeOqhyTUHR40DsDOWyt7OaKxpQ7eFYqysw@mail.gmail.com
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
List pgsql-hackers
Thanks Michael!

This is a known issue with exclusive backups, which is a reason why
non-exclusive backups have been implemented.  pg_basebackup does that,
and using "false" as the third argument of pg_start_backup() would
have the same effect.  So I would recommend to switch to that.

Is there a plan in place to remove the exclusive backup option from the core in PG 15/16? If we are keeping it then why not make it better? 

pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: row filtering for logical replication
Next
From: Amit Kapila
Date:
Subject: Re: pg_upgrade and publication/subscription problem