Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Sailesh Krishnamurthy wrote: > >> Does pgsql only record X locks on the individual tuples on-disk or > >> does it do so for S locks as well ? > > > We don't need to shared lock individual rows because of MVCC --- well, > > we sort of do by recording our xid in our proc structure, so folks don't > > change things underneath us. We prevent expired rows from disappearing > > from the disk by others looking at our proc start xid. > > This is actually an issue though. Row-level shared locks would be > really nice to have for foreign-key handling. Right now we have to > use X locks for those, and that leads to deadlocking problems for > applications.
Is the plan to allow one backend to shared lock the row while others can read it but not modify it, or is the idea to actually allow multiple backends to record their shared status on the row? -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
