Joshua D. Drake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 11 Mar 2008 16:17:53 -0400 (EDT) > Bruce Momjian <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
