On Thu, Aug 7, 2008 at 12:38 PM, Simon Riggs wrote: > I propose creating "Visibility Groups" that *explicitly* limit the > ability of a transaction to access data outside its visibility group(s).
Doesn't every transaction need to access data from the catalogs? Wouldn't the inclusion of a catalogs visibility group in every transaction negate any potential benefits? > Once set, any attempt to lock an object outside of a transactions > defined visibility_groups will result in an error: Or is this about locking and not about data access? Jochem -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers