Re: [HACKERS] PATCH: Make pg_stop_backup() archive wait optional - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] PATCH: Make pg_stop_backup() archive wait optional
Date
Msg-id CAB7nPqRf6LnNN3TZZGi5DJ8sTWE5XekBSAj7E0CqsJ1nDGhiEA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] PATCH: Make pg_stop_backup() archive wait optional  (David Steele <david@pgmasters.net>)
Responses Re: [HACKERS] PATCH: Make pg_stop_backup() archive wait optional  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On Tue, Feb 28, 2017 at 9:25 AM, David Steele <david@pgmasters.net> wrote:
> I also marked the pg_stop_* functions as parallel restricted, the same
> as pg_start_backup().  Previously they were parallel safe which I don't
> believe is accurate for the non-exclusive version at the very least,
> since it is tied to a particular backend.

Yeah, those should really be parallel restricted. For the exclusive
version, having the function run in parallel would also lead to errors
per the presence/lack of backup_label file.
-- 
Michael



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [HACKERS] Creation of "Future" commit fest, named 2017-07
Next
From: David Steele
Date:
Subject: Re: [HACKERS] PATCH: Make pg_stop_backup() archive wait optional