Re: PANIC in pg_commit_ts slru after crashes

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Jeff Janes <jeff(dot)janes(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 10:44:22
Message-ID: CAB7nPqQ05T0PVAZenQ_dcxwkt0ggPpdv-s5fSyV15HYB+CNVZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 18, 2017 at 7:05 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> I've added a recheck in ProcessTwoPhaseBuffer() after we acquire the lock.
>
> If its worth acquiring the lock its worth checking we don't have a race.

I see. No objections to that.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2017-04-18 10:54:30 Re: Failed recovery with new faster 2PC code
Previous Message Michael Paquier 2017-04-18 10:39:36 Re: Continuous buildfarm failures on hamster with bin-check