Re: non-exclusive backup cleanup is mildly broken - Mailing list pgsql-hackers

From David Steele
Subject Re: non-exclusive backup cleanup is mildly broken
Date
Msg-id 0c930fd0-ce3a-5ba7-a3a6-26c036f08db3@pgmasters.net
Whole thread Raw
In response to Re: non-exclusive backup cleanup is mildly broken  (Magnus Hagander <magnus@hagander.net>)
Responses Re: non-exclusive backup cleanup is mildly broken  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
On 12/13/19 3:56 AM, Magnus Hagander wrote:
> On Fri, Dec 13, 2019 at 9:00 AM Michael Paquier <michael@paquier.xyz 
> 
>     I think that's a bad idea to put a restriction of this kind.  There
>     are large consumers of 2PC, and everybody needs backups.
> 
> 
> You misunderstood me. I certainly didn't mean that people who use 2PC 
> shouldn't be able to use proper backups -- that would be *terrible*.
> 
> I meant disallowing pg_start_backup() in a session that had a prepared 
> transaction, and disallowing preparing a transaction in a session with 
> an ongoing backup. They would still work perfectly fine in *other* 
> parallel sessions.

+1.  I think it is reasonable to expect pg_start/stop_backup() to be 
performed in its own session without prepared transactions.

+more if this concession keeps other aspects of the code simpler.

-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: xlog.c variable pointlessly global
Next
From: Peter Geoghegan
Date:
Subject: Re: Why is get_actual_variable_range()'s use of SnapshotNonVacuumablesafe during recovery?