| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, harukat(at)sraoss(dot)co(dot)jp, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |
| Date: | 2016-07-12 23:05:16 |
| Message-ID: | 13701.1468364716@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> On Tue, Jul 12, 2016 at 2:02 PM, <harukat(at)sraoss(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-07-13 01:06:41 | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |
| Previous Message | Alvaro Herrera | 2016-07-12 22:54:04 | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |