| From: | "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com> |
|---|---|
| To: | pgsql-docs(at)postgresql(dot)org |
| Subject: | ROW SHARE/SELECT ... FOR UPDATE + foreign keys |
| Date: | 2005-07-21 19:47:40 |
| Message-ID: | 7B27AD9D-67FC-47BE-9956-B4066E6B9C53@sitening.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F. O'Connell | 2005-07-21 20:32:28 | Beta Docs |
| Previous Message | Halley Pacheco de Oliveira | 2005-07-17 12:04:25 | PostgreSQL 8.0.3 Documentation - Chapter 21. Routine Database Maintenance Tasks |