Tom Lane <t...@sss.pgh.pa.us> wrote: > Shouldn't we make the autovac launcher use READ COMMITTED, too? Anything which starts a transaction and doesn't need to use a transaction-lifetime snapshot plus SIRead locks to achieve truly serializable behavior should probably be ignoring default_transaction_isolation and forcing READ COMMITTED. I would think that should include the autovac launcher. Probably *any* of the background processes which can get a start a transaction should force READ COMMITTED. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
