| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jonesbl(at)WellsFargo(dot)COM |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_dumpall / pg_dump |
| Date: | 2003-05-02 21:13:52 |
| Message-ID: | 2602.1051910032@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
jonesbl(at)WellsFargo(dot)COM writes:
> My problem is, the dump takes more that 15 minutes and there doesn't seem to
> be any way to temporarily increase the timeout value a la:
> & psql -c "set statement_timeout = 0;" <dbname>
> & pg_dumpall ...
> & psql -c "set statement_timeout = 900000;" <dbname>
The grotty way is
export PGOPTIONS="--statement_timeout=0"
pg_dumpall
unset PGOPTIONS
A possibly more convenient answer is to set statement_timeout=0 as a
per-user setting for the superuser (see ALTER USER). Or, if you want
the limit to apply to superuser too, create a second superuser account
that you use only for pg_dump, vacuumdb, and similar long jobs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Kiger | 2003-05-02 21:35:40 | md5 in postgres 7.3 |
| Previous Message | Tom Lane | 2003-05-02 21:10:53 | Re: vacuum locks up database |