From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | 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 22:54:04 |
Message-ID: | 20160712225404.GA892041@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Amit Kapila wrote:
> On Tue, Jul 12, 2016 at 2:02 PM, <harukat(at)sraoss(dot)co(dot)jp> wrote:
> > C:\Program Files\PostgreSQL\9.6\data\base\16393>dir /q 16444
> >
> > C:\Program Files\PostgreSQL\9.6\data\base\16393 directory
> >
> > 2016/07/12 15:56 0 ... 16444
> >
> > Dir command says the file 16444's owner is '...'.
> > It means file 16444 is in STATUS_DELETE_PENDING.
> pg_basebackup tries to backup all the files in data directory and
> tablespaces. Refer Notes section of pg_basebackup documentation. I
> think if it decides to skip a file with some bad status, it might also
> lead to a corrupt backup. I wonder how the file has such a status?
> From the name, it looks to be a valid database file.
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.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-07-12 23:05:16 | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |
Previous Message | Tom Lane | 2016-07-12 21:11:32 | Re: BUG #14245: Segfault on weird to_tsquery |