Re: Re: [COMMITTERS] pgsql: Fix an assertion failure related to an exclusive backup.

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Fix an assertion failure related to an exclusive backup.
Date: 2017-01-17 22:18:14
Message-ID: CAB7nPqQ5WvbUSNzXK922vYdTJvEFWnBOsw0r3aPkKNMfk-d7EA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Jan 17, 2017 at 11:42 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> With the patch, what happens if pg_stop_backup exits with an error
> after removing backup_label file before resetting the backup state
> to none?

Removing the backup_label file is the last error that can happen
during the time the callback is set. And the counter is reset
immediately after.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-01-17 22:53:36 Re: [COMMITTERS] pgsql: Generate fmgr prototypes automatically
Previous Message Alvaro Herrera 2017-01-17 21:35:48 Re: [COMMITTERS] pgsql: Generate fmgr prototypes automatically

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-01-17 22:31:46 Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait
Previous Message Robert Haas 2017-01-17 22:12:47 Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait