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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
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-01 09:53:52
Message-ID: CAB7nPqQ6r6Ye88BVN+eXWa3qJnng801m4VE151oKtnbGDF2Rtw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jyoti Leeka 2017-01-02 10:02:45 Postgres returning in-correct results with ST_DWithin()
Previous Message Michael Paquier 2017-01-01 00:06:45 Re: [BUG] pg9.4.10 Logical decoding did not get the correct oldtuplelen