Simon Riggs <si...@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
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
