| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "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 07:31:46 |
| Message-ID: | 20070418073146.GA20431@svr2.hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 17, 2007 at 10:33:21PM -0400, Bruce Momjian wrote:
> 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.
I'd suggest doing both. Tell people that it's dangerous (probably to the
point of a comment in the sample config file), but *also* force it in
pg_dump since you can't really expect people to read the documentation.
//MAgnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Russell Smith | 2007-04-18 07:41:26 | Re: Grantor name gets lost when grantor role dropped |
| Previous Message | Martin Langhoff | 2007-04-18 06:39:34 | Re: Hacking on PostgreSQL via GIT |