Re: autovacuum and default_transaction_isolation

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> 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.

AFAIK only the autovac processes can run transactions.  We'll need to
keep this in mind if we ever create other background processes that
can do so, though.

For the moment I duplicated the existing logic of overriding relevant
GUC variables in the process's Main() function, but I wonder if we ought
to be setting these things in some more centralized place, like
InitPostgres().  That function already knows quite a bit about what
sort of process it's initializing ...
        regards, tom lane