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

[Sorry for hanging to wrong message but I cannot get any email from
the list since this morning and I have to create a email from the
archive (posting is ok using the same email account. See my From:).]

Since no one came up with any useful solution for this soon, I think
I need to add this to the TODO list unless there's an objection.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

> 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, 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
>