Date: Wed, 3 Aug 2016 14:18:24 +0900
From: TAKATSUKA Haruka <harukat@sraoss.co.jp>
To: PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Subject: Re: BUG #14243: pg_basebackup failes by a
 STATUS_DELETE_PENDING file
Message-Id: <20160803141824.0f5f5c16.harukat@sraoss.co.jp>
In-Reply-To: 
 <CAB7nPqSWKjJMCkNTB8qikcjdYDtwcmCeasEquWKtanAfp2OTXw@mail.gmail.com>
References: <20160712225404.GA892041@alvherre.pgsql>
	<13701.1468364716@sss.pgh.pa.us>
	<CAB7nPqTq0O+edHm8buV2s6SEV6WsdEDysWKeOunpiOgLWLSSCg@mail.gmail.com>
	<CAB7nPqSWKjJMCkNTB8qikcjdYDtwcmCeasEquWKtanAfp2OTXw@mail.gmail.com>
Organization: SRA OSS,Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org


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@sraoss.co.jp


On Wed, 13 Jul 2016 10:10:37 +0900
Michael Paquier <michael.paquier@gmail.com> wrote:

> On Wed, Jul 13, 2016 at 10:06 AM, Michael Paquier
> <michael.paquier@gmail.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


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs