Re: Autovacuum vs statement_timeout - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Autovacuum vs statement_timeout
Date
Msg-id 20070418153004.GA19598@alvh.no-ip.org
Whole thread Raw
In response to Re: Autovacuum vs statement_timeout  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: Autovacuum vs statement_timeout  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Autovacuum vs statement_timeout  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-hackers
Robert Treat wrote:
> On Tuesday 17 April 2007 20:54, Tom Lane wrote:

> > I'm not excited about the other ones but I can see the argument for
> > making pg_dump force the timeout to 0.
> 
> Allowing pg_dump to run un-checked could also lead to problems such as 
> exceeding maintenence windows causing performance issues, or causing trouble 
> due to lock contention with ongoing pg_dumps.

I have never ever seen a request to be able to control pg_dump and have
it stop dumping if the time taken to dump exceeded a threshold.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Harvell F
Date:
Subject: Re: Backend Crash
Next
From: Alvaro Herrera
Date:
Subject: Re: Autovacuum vs statement_timeout