On Wed, Mar 7, 2012 at 10:18 AM, Gokulakannan Somasundaram <gokul...@gmail.com> wrote: >> >> Insert, Update and Delete don't take locks they simply mark the tuples >> they change with an xid. Anybody else wanting to "wait on the lock" >> just waits on the xid. We do insert a lock row for each xid, but not >> one per row changed. > > I mean the foreign key checks here. They take a Select for Share Lock right. > That's what we are trying to optimize here. Or am i missing something? So by > following the suggested methodology, the foreign key checks won't take any > locks.
Please explain in detail your idea of how it will work. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers