From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Autovacuum vs statement_timeout |
Date: | 2008-03-11 20:36:21 |
Message-ID: | 200803112036.m2BKaLU22844@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 11 Mar 2008 16:17:53 -0400 (EDT)
> Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> > Greg Sabino Mullane wrote:
> > > > Particularly consider using psql to restore a pg_dump
> > > > dump --- are we going to add "SET statement_timeout=0"
> > > > to the pg_dump file?
> > >
> > > I hope not. That should be the user's choice.
> >
> > Would anyone want to limit the load time for pg_dump? I can hardly
> > see why.
>
> I have to agree with Bruce here. You restore a backup because your
> hosed something or you are building a dev environment. These are both
> boolean results that should end in TRUE :)
But maybe this brings up that people just shouldn't put
statement_timeout in postgresql.conf, and if they do, they deserve what
they get.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Denne | 2008-03-11 20:43:11 | Re: Estimating geometric distributions |
Previous Message | Joshua D. Drake | 2008-03-11 20:32:45 | Re: Autovacuum vs statement_timeout |