Nicolas Barbier wrote: > Therefore, with next-key locking you better don't have too many table > scans if you want to have any concurrent transactions. Well, I would say that you don't want too many table scans on heavily updated tables if you don't want too many serialization failures. Keep in mind that the SIREAD locks would not block anything. A dangerous structure, involving two adjacent rw dependencies, must be found before anything is rolled back. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
