| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Markus Wanner <markus(at)bluegap(dot)ch>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deadlock bug |
| Date: | 2010-08-25 17:02:48 |
| Message-ID: | 4C754CB8.5000406@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> It strikes me that a possibly useful simplification of the idea is a
> lock type that allows HOT updates and not non-HOT ones; or more
> precisely not ones that change any indexed columns --- if the row ends
> up having to go off-page for lack of space, that need not concern us.
While an improvement over the current, that's still more restrictive
than we actually need for FKs. FKs just need to lock the value of the
reference column(s); they don't care if *other* indexes are updated.
Thus, for an RI reference, we care about one and exactly one unique/PK
index on the referenced table.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2010-08-25 17:15:07 | Re: git: uh-oh |
| Previous Message | Stephen Frost | 2010-08-25 16:57:56 | Re: Performance Farm Release |