Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Date: 2017-01-04 09:52:51
Message-ID: CABUevExHmABHM==fX9WzLop68nCNaH71dafH9=wnXXcwixYdEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Jan 1, 2017 at 10:53 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:

> On Sat, Dec 31, 2016 at 9:27 PM, Magnus Hagander <magnus(at)hagander(dot)net>
> wrote:
> > So, we're still with zero ability to reproduce this problem enough to
> know
> > if it's fixed, or if other issues are caused.
> >
> > I'm thinking maybe we should push this patch to master, to at least get a
> > largeish number of runs with it on a bunch of different platforms. No
> > backpatching until we've seen it run there for some time to feel more
> > confident about it.
> >
> > Thoughts?
>
> Yeah, I kind of agree with that. Not reacting with an ENOENT on
> win32's stat() if ERROR_DELETE_PENDING is found is definitely wrong,
> as is not doing the mapping in win32error.c.
>

OK, I've pushed it to master. Let's leave it there for a while and then
decide what to do about backpatching. Re-visit in time for the next minor
releases perhaps?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2017-01-04 10:10:34 Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Previous Message marc 2017-01-04 08:56:05 BUG #14484: ERROR: missing chunk number 0 for toast value