| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: Autovacuum vs statement_timeout |
| Date: | 2007-04-17 19:51:51 |
| Message-ID: | 46252557.6090409@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim C. Nasby wrote:
> On Sun, Apr 01, 2007 at 12:36:01AM +0200, Peter Eisentraut wrote:
>> Tom Lane wrote:
>>> I seem to remember that we'd agreed that autovacuum should ignore any
>>> globally set statement_timeout, on the grounds that a poorly chosen
>>> setting could indefinitely prevent large tables from being vacuumed.
>> On a vaguely related matter, should programs such as pg_dump, vacuumdb,
>> and reindexdb disable statement_timeout?
>
> Youch... yes, they should IMO. Add clusterdb, pg_dumpall and pg_restore
> to that list as well (really, pg_dump(all) should output a command to
> disable statement_timeout).
I don't know if that should be a default or not. It is certainly easy
enough to disable it should you want to.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sharath kumar | 2007-04-17 19:59:33 | schema creation during initdb |
| Previous Message | Jim C. Nasby | 2007-04-17 19:26:16 | Re: Autovacuum vs statement_timeout |