public inbox for [email protected]
help / color / mirror / Atom feedFrom: Thomas F. O'Connell <[email protected]>
To: [email protected]
Subject: ROW SHARE/SELECT ... FOR UPDATE + foreign keys
Date: Thu, 21 Jul 2005 14:47:40 -0500
Message-ID: <[email protected]> (raw)
What would people think of adding a note to the ROW SHARE section of
Table-Level Locks remarking on the fact that referential integrity
checks expressed through foreign keys do SELECT ... FOR UPDATES.
http://www.postgresql.org/docs/8.0/static/explicit-
locking.html#LOCKING-TABLES
It was somewhat challenging today to try to track down a pervasive
locking issue related to a table not directly referenced in a stored
procedure but that was referenced by a key in a table that was being
updated.
I'm not sure how this changes with the new shared row locking
implementation in 8.1...
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
view thread (2+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: ROW SHARE/SELECT ... FOR UPDATE + foreign keys
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox