| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-09-29 07:31:16 |
| Message-ID: | CAB7nPqSK9ETa81PWHKJT26hFaf_dhMcP9X6AaHHR5Z6vNvdzgA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Sep 21, 2016 at 1:17 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-09-29 07:38:34 | Re: BUG #14243: pg_basebackup failes by a STATUS_DELETE_PENDING file |
| Previous Message | David Rowley | 2016-09-29 05:41:21 | Re: BUG #14344: string_agg(DISTINCT ..) crash |