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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, TAKATSUKA Haruka <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-10-06 05:20:38
Message-ID: CAB7nPqQ4EQ4-HpjKT_UPp-3xZCnm2pQK-OK_b75uqXqhKz9JNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Sep 29, 2016 at 11:34 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Michael Paquier wrote:
>
>> I gave this bug another try and let Windows run for some time but I
>> cannot reproduce the original failure even with manual checkpointing
>> and aggressive checkpoint_timeout, while truncating relations heavily
>> with pgbench to enforce the deletion of relfilenodes. To all, do you
>> think that having a large relfilenode file matters to trigger this
>> issue?
>
> Hmm, perhaps with a larger file the OS spends more time shredding the
> file or something like that? Perhaps there are filesystem options
> involved, for instance.

I have been digging around that, but could not find out any options
that would delay the file deletion after it has been requested. As
pg_basebackup grabs automatically all the files in PGDATA, I have as
well tried to use thousands of dummy files up to 1MB, as well as huge
files ("fsutil file createnew" is your friend), deleting them manually
to force the stat() calls to be unhappy be still I could not reproduce
it... If somebody has better ideas I am open.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2016-10-06 06:31:30 Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Previous Message Peter Geoghegan 2016-10-06 02:47:52 Re: BUG #14343: UPSERT (ON CONFLICT) doesn't check ON CONFLICT constraint first