| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-08-16 19:54:22 |
| Message-ID: | 20160816195422.rhsptgx2ijvlgab6@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2016-07-12 19:05:16 -0400, Tom Lane wrote:
> 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.
One approach would be to rename the file into something indicating it's
being deleted, before actually deleting it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-08-16 22:51:24 | Re: BUG #14150: Attempted to delete invisible tuple |
| Previous Message | Mephysto | 2016-08-16 16:26:18 | Re: jsonb_array_elements issue |