Re: pg_dumpall / pg_dump - Mailing list pgsql-admin

From Tom Lane
Subject Re: pg_dumpall / pg_dump
Date
Msg-id 2602.1051910032@sss.pgh.pa.us
Whole thread Raw
In response to pg_dumpall / pg_dump  (jonesbl@WellsFargo.COM)
List pgsql-admin
jonesbl@WellsFargo.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


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: vacuum locks up database
Next
From: Kris Kiger
Date:
Subject: md5 in postgres 7.3