Re: pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait
Date
Msg-id CA+U5nM+k_eEB8QO60QuPxWhyjPLzhTGVVsjapvA8a0Ow6JLJjg@mail.gmail.com
Whole thread Raw
In response to pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait
List pgsql-committers
On Tue, Aug 2, 2011 at 6:24 PM, Tom Lane <tgl@sss.pgh.pa.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

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait
Next
From: Tom Lane
Date:
Subject: pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place.