Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Resolve timing issue with logging locks for Hot Standby. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Resolve timing issue with logging locks for Hot Standby.
Date
Msg-id 21607.1327883402@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Resolve timing issue with logging locks for Hot Standby.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pgsql: Resolve timing issue with logging locks for Hot Standby.  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-committers
Tree view 
Simon Riggs <simon@2ndQuadrant.com> writes:
> Resolve timing issue with logging locks for Hot Standby.
> We log AccessExclusiveLocks for replay onto standby nodes,
> but because of timing issues on ProcArray it is possible to
> log a lock that is still held by a just committed transaction
> that is very soon to be removed. To avoid any timing issue we
> avoid applying locks made by transactions with InvalidXid.

> Simon Riggs, bug report Tom Lane, diagnosis Pavan Deolasee

I see this was only applied to HEAD.  Wouldn't back-patching be in
order?  The problem is in 9.1 as well, no?

            regards, tom lane

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Assorted comment fixes, mostly just typos, but some obsolete sta
Next
From: marian@pgfoundry.org (User Marian)
Date:
Subject: jsonpath - postgresql-json: Fix bug: json_check not crash if json is