Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Resolve timing issue with logging locks for Hot Standby.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Resolve timing issue with logging locks for Hot Standby.
Date: 2012-01-30 00:30:02
Message-ID: 21607.1327883402@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
Simon Riggs <simon(at)2ndQuadrant(dot)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

In response to

Responses

pgsql-committers by date

Next:From: User MarianDate: 2012-01-30 08:22:32
Subject: jsonpath - postgresql-json: Fix bug: json_check not crash if json is
Previous:From: Tom LaneDate: 2012-01-30 00:24:22
Subject: pgsql: Assorted comment fixes, mostly just typos,but some obsolete sta

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group