Re: pgsql: Prevent autovacuum transactions from running in serializable mod

From: Andrew Dunstan <andrew(dot)dunstan(at)pgexperts(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Prevent autovacuum transactions from running in serializable mod
Date: 2011-11-30 04:03:31
Message-ID: 4ED5AB13.7050501@pgexperts.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 11/29/2011 10:40 PM, Tom Lane wrote:
> Prevent autovacuum transactions from running in serializable mode.
>
> Force the transaction isolation level to READ COMMITTED in autovacuum
> worker and launcher processes. There is no benefit to using a higher
> isolation level, and doing so could result in delaying foreground
> transactions (or maybe even causing unnecessary serialization failures?).
> Noted by Dan Ports.
>
> Also, make sure we disable zero_damaged_pages and statement_timeout in
> the autovac launcher, not only workers. Now that the launcher can run
> transactions, these settings could affect its behavior, and it seems
> like the same arguments apply to the launcher as the workers.
>
>

Looks like this broke the buildfarm.

cheers

andrew

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2011-11-30 04:05:31 Re: pgsql: Prevent autovacuum transactions from running in serializable mod
Previous Message Tom Lane 2011-11-30 03:40:29 pgsql: Prevent autovacuum transactions from running in serializable mod