pgsql: Unbreak lock conflict detection for Hot Standby.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Unbreak lock conflict detection for Hot Standby.
Date: 2013-01-18 17:17:23
Message-ID: E1TwFZD-0001lh-26@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Unbreak lock conflict detection for Hot Standby.

This got broken in the original fast-path locking patch, because
I failed to account for the fact that Hot Standby startup process
might take a strong relation lock on a relation in a database to
which it is not bound, and confused MyDatabaseId with the database
ID of the relation being locked.

Report and diagnosis by Andres Freund. Final form of patch by me.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/d8c3896626e9fa48c9ebadc31850d54a791a08e3

Modified Files
--------------
src/backend/storage/lmgr/lock.c | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2013-01-18 19:03:32 pgsql: Rename new latex longtable function name, for consistency
Previous Message Bruce Momjian 2013-01-18 14:26:58 pgsql: Improve pg_upgrade error report