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

From Tom Lane
Subject Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Date
Msg-id 13701.1468364716@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
List pgsql-bugs
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.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Next
From: Michael Paquier
Date:
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file