Re: PANIC in pg_commit_ts slru after crashes

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PANIC in pg_commit_ts slru after crashes
Date: 2017-04-18 08:51:58
Message-ID: CANP8+jJcnKab54D+RO0DHTOejQ-b5cQqf_XntF1Z1YOTLL4ihA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17 April 2017 at 16:33, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Sun, Apr 16, 2017 at 6:59 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
> wrote:
>>
>>
>>
>> Jeff, does this patch make the situation better? The fix is rather
>> simple as it just makes sure that the next XID never gets updated if
>> there are no 2PC files.
>
>
> Yes, that fixes the reported case when 2PC are not being used.

Thanks Jeff.

I certainly prefer the simplicity of Michael's approach. I'll move to commit.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kang Yuzhe 2017-04-18 08:52:05 Re: On How To Shorten the Steep Learning Curve Towards PG Hacking...
Previous Message Kang Yuzhe 2017-04-18 08:33:17 Re: On How To Shorten the Steep Learning Curve Towards PG Hacking...