Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
Date
Msg-id CAB7nPqSK9ETa81PWHKJT26hFaf_dhMcP9X6AaHHR5Z6vNvdzgA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file
List pgsql-bugs
On Wed, Sep 21, 2016 at 1:17 PM, Michael Paquier
<michael.paquier@gmail.com> 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?
>
> Could it be possible to get more testing as well? We won't go far as
> long as we have not checked that the issue gets fixed by the proposed
> patch in a place where the problem is able to show up.

I still cannot reproduce the original problem, so there is not much I
can do to validate the patch.. If someone has ways to check that the
fix works as expected that would be nice. For now I am marking this
patch as returned with feedback in the CF app until this happens.
--
Michael

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #14344: string_agg(DISTINCT ..) crash
Next
From: Magnus Hagander
Date:
Subject: Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file