Re: autovacuum and default_transaction_isolation - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: autovacuum and default_transaction_isolation
Date
Msg-id 4ED5258C020000250004360A@gw.wicourts.gov
Whole thread Raw
In response to Re: autovacuum and default_transaction_isolation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: autovacuum and default_transaction_isolation
List pgsql-hackers
Tom Lane <tgl@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


pgsql-hackers by date:

Previous
From: Joe Abbate
Date:
Subject: Reserved words and delimited identifiers
Next
From: Dan Ports
Date:
Subject: Re: autovacuum and default_transaction_isolation