Re: Bug in StartupSUBTRANS - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Bug in StartupSUBTRANS
Date
Msg-id CAMkU=1x+fq6nnK6twnUxW_qFDkqrReexjrTLZsyaz9PETkU9Eg@mail.gmail.com
Whole thread Raw
In response to Re: Bug in StartupSUBTRANS  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Bug in StartupSUBTRANS
Re: Bug in StartupSUBTRANS
List pgsql-hackers
On Tue, Feb 9, 2016 at 10:33 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 9 February 2016 at 18:42, Jeff Janes <jeff.janes@gmail.com> wrote:
>>
>> While testing the crash resilience of the recent 2-part-commit
>> improvements, I've run into a problem where sometimes after a crash
>> the recovery process creates zeroed files in pg_subtrans until it
>> exhausts all disk space.
>
>
> Not sure which patch you're talking about there (2-part-commit).

The one here:

commit 978b2f65aa1262eb4ecbf8b3785cb1b9cf4db78e
Author: Simon Riggs <simon@2ndQuadrant.com>
Date:   Wed Jan 20 18:40:44 2016 -0800

    Speedup 2PC by skipping two phase state files in normal path

I thought there was a second commit in the series, but I guess that is
still just proposed.  I've haven't tested that one, just the committed
one.

I've repeated the crash/recovery/wrap-around testing with the proposed
fix in place, and this pre-existing problem seems to be fixed now, and
I have found no other problems.

I've attached a new version, incorporating comments from Tom and Michael.

Cheers,

Jeff

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: extend pgbench expressions with functions
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl