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/


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq