Re: pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait
Date: 2011-08-02 19:16:06
Message-ID: CA+U5nM+k_eEB8QO60QuPxWhyjPLzhTGVVsjapvA8a0Ow6JLJjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Aug 2, 2011 at 6:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Fix incorrect initialization of ProcGlobal->startupBufferPinWaitBufId.
>
> It was initialized in the wrong place and to the wrong value.  With bad
> luck this could result in incorrect query-cancellation failures in hot
> standby sessions, should a HS backend be holding pin on buffer number 1
> while trying to acquire a lock.

Did I miss a bug report?

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-08-02 19:17:13 pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place.
Previous Message Tom Lane 2011-08-02 17:24:23 pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait