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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
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-07-13 01:10:37
Message-ID: CAB7nPqSWKjJMCkNTB8qikcjdYDtwcmCeasEquWKtanAfp2OTXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 13, 2016 at 10:06 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Checking directly for STATUS_DELETE_PENDING would be the way to go,
> likely with tweaks in basebackup.c. but like Takatsuka-san, I cannot
> find anything around that would allow us to check for that.
>
> [1]: http://stackoverflow.com/questions/6680491/why-does-windows-return-error-access-denied-when-i-try-to-open-a-delete-pended-f

Actually we may want to tweak stat() to not complain for a file with
such a state.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2016-07-13 02:56:32 Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL
Previous Message Michael Paquier 2016-07-13 01:06:41 Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file