Re: PATCH: Make pg_stop_backup() archive wait optional

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: Make pg_stop_backup() archive wait optional
Date: 2017-02-28 00:38:16
Message-ID: CAB7nPqRf6LnNN3TZZGi5DJ8sTWE5XekBSAj7E0CqsJ1nDGhiEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 28, 2017 at 9:25 AM, David Steele <david(at)pgmasters(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2017-02-28 00:42:55 Re: PATCH: Make pg_stop_backup() archive wait optional
Previous Message David Steele 2017-02-28 00:28:29 Re: Creation of "Future" commit fest, named 2017-07