Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile
Date
Msg-id CABUevExHmABHM==fX9WzLop68nCNaH71dafH9=wnXXcwixYdEA@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile
List pgsql-bugs


On Sun, Jan 1, 2017 at 10:53 AM, Michael Paquier <michael.paquier@gmail.com> wrote:
On Sat, Dec 31, 2016 at 9:27 PM, Magnus Hagander <magnus@hagander.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?
 
--

pgsql-bugs by date:

Previous
From: marc@intershop.de
Date:
Subject: [BUGS] BUG #14484: ERROR: missing chunk number 0 for toast value
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDINGfile