Re: Autovacuum vs statement_timeout - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Autovacuum vs statement_timeout
Date
Msg-id 200704180233.l3I2XL226380@momjian.us
Whole thread Raw
In response to Re: Autovacuum vs statement_timeout  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Autovacuum vs statement_timeout
List pgsql-hackers
Alvaro Herrera wrote:
> I think that is too strong an assumption, which is why I'm planning to
> back-patch the change to reset statement_timeout to 0 on autovacuum till
> 8.0, as discussed.  I think I should also backpatch the change to set
> zero_damaged_pages as well (which is not on 8.0 AFAIR).
> 
> It's very very easy to change things in postgresql.conf.  Actually
> knowing what you are doing (i.e. thinking on the consequences on VACUUM
> and such) is a whole another matter.

Frankly, setting statement_timeout in postgresql.conf seems so risky in
so many ways, perhaps we just need to document that the parameter
probably should not be set in postgresql.conf, and why.

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [COMMITTERS] pgsql: Update error message for COPY with a multi-byte delimiter.
Next
From: Tom Lane
Date:
Subject: Re: Hacking on PostgreSQL via GIT