| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: Autovacuum vs statement_timeout |
| Date: | 2007-04-18 02:33:21 |
| Message-ID: | 200704180233.l3I2XL226380@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-18 05:33:14 | Re: Hacking on PostgreSQL via GIT |
| Previous Message | Bruce Momjian | 2007-04-18 02:28:45 | Re: [COMMITTERS] pgsql: Update error message for COPY with a multi-byte delimiter. |