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

From Robert Haas
Subject Re: non-exclusive backup cleanup is mildly broken
Date
Msg-id CA+TgmoYxnjL43p-_x+Bq60uPXJ1Z43k0pSwcnhzzOzJ5T5FjwQ@mail.gmail.com
Whole thread Raw
In response to Re: non-exclusive backup cleanup is mildly broken  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: non-exclusive backup cleanup is mildly broken  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Dec 17, 2019 at 11:36 PM Fujii Masao <masao.fujii@gmail.com> wrote:
> If pg_abort_backup callback function can be called safely even when
> the backup is not in progress, we can just use the global variable like
> pg_abort_backup_registered to register the callback function only
> on first call. In this way, cancel_before_shmem_exit() doesn't need to
> search the array to get rid of the function.

Right. That's how the proposed patch works.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Block level parallel vacuum
Next
From: Prabhat Sahu
Date:
Subject: Re: [HACKERS] Block level parallel vacuum