From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: harukat@sraoss.co.jp, PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Date: Tue, 12 Jul 2016 19:05:16 -0400
Message-ID: <13701.1468364716@sss.pgh.pa.us> (raw)
In-Reply-To: <20160712225404.GA892041@alvherre.pgsql>
References: <20160712225404.GA892041@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, amit.kapila16@gmail.com
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
In-Reply-To: <13701.1468364716@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox