Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Date
Msg-id 20160816195422.rhsptgx2ijvlgab6@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file  (Magnus Hagander <magnus@hagander.net>)
List pgsql-bugs
On 2016-07-12 19:05:16 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> >> On Tue, Jul 12, 2016 at 2:02 PM,  <harukat@sraoss.co.jp> wrote:
> >>> It means file 16444 is in STATUS_DELETE_PENDING.
>
> > This file is probably being deleted by a checkpoint after some user
> > transaction marked it for removal (either because the relation was
> > dropped, or because it got a new relfilenode).  I would say that the
> > file is not needed for the backup after all and pg_basebackup should
> > just ignore it.
>
> Yeah.  The question is how do we distinguish that from cases that
> are less benign.

One approach would be to rename the file into something indicating it's
being deleted, before actually deleting it.

pgsql-bugs by date:

Previous
From: Mephysto
Date:
Subject: Re: jsonb_array_elements issue
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #14150: Attempted to delete invisible tuple