"Kevin Grittner" <kevin.gritt...@wicourts.gov> writes: > I'm reviving the discussion on the subject topic because I just had > an epiphany which makes it seem simple to implement. The concept of > this is that if you start a SERIALIZABLE READ ONLY transaction in an > SSI environment when certain conditions are true, it doesn't need to > acquire predicate locks or test for rw-conflicts.
I assume this would have to be a "hard" definition of READ ONLY, not the rather squishy definition we use now? How would we manage the compatibility implications? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers