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

From: TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp>
To: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Date: 2016-08-03 05:18:24
Message-ID: 20160803141824.0f5f5c16.harukat@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


I study this a little more, but I cannot find the way to distinguish
STATUS_DELETE_PENDING state from the other state that causes permission
denied error.

Cmd.exe's "dir /q" may distinguish these, but I cannot know which API
is used.

-----------------
Haruka Takatsuka
harukat(at)sraoss(dot)co(dot)jp

On Wed, 13 Jul 2016 10:10:37 +0900
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:

> 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

Browse pgsql-bugs by date

  From Date Subject
Next Message Tatsuo Ishii 2016-08-03 05:33:41 Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Previous Message Michael Paquier 2016-08-03 00:14:10 Re: BUG #14273: Tuple concurently updated error while creating function using async call from node js with postgresq