pg_dumpall / pg_dump

From: jonesbl(at)WellsFargo(dot)COM
To: pgsql-admin(at)postgresql(dot)org
Subject: pg_dumpall / pg_dump
Date: 2003-05-02 18:31:24
Message-ID: EC3A956C8957BE4C80D15D9F5A8B8005116DF5@msgsw55cacah09.wellsfargo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Postgres ver. 7.3.1, on HPUX.

I'm having a problem dumping my database using pg_dumpall. The
statement_timeout value is set to 15 minutes, and I don't want to set it
higher (protecting the db against long and/or ill formed queries).

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>

I did hack the vacuumdb script to alter the timeout value so VACUUM would
complete (takes 1 hour 30 minutes).

Is there any way to hack pg_dump and pg_dumpall to temporarily increase
statement_timeout limits so backups can complete? Or, better yet, is there
an undocumented command to alter the statement_timeout value during the
dump?

Bill Jones
Systems Architect
Middleware Services
Wells Fargo Services Company
Office --415.243.1364
PCS -- 415.254.3831 (4152543831(at)mobile(dot)att(dot)net)

Views expressed are mine. Only in unusual circumstances are they shared by
my employer.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message jonesbl 2003-05-02 18:33:18 vacuum locks up database
Previous Message Stephan Szabo 2003-05-02 16:18:30 Re: Changing colums type