Re: statement timeout vs dump/restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: statement timeout vs dump/restore
Date: 2008-05-03 17:01:36
Message-ID: 9542.1209834096@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Do we want the following:

> 1. pg_dump issues "set statement_timeout = 0;" to the database prior to
> taking its copy of data (yes/no/default-but-switchable)
> 2. pg_dump/pg_restore issue "set statement_timeout = 0;" in text mode
> output (yes/no/default-but-switchable)
> 3. pg_restore issues "set statement_timeout = 0;" to the database in
> restore mode (yes/no/default-but-switchable)

I think "yes" for all three. There was some handwaving about someone
maybe not wanting it, but an utter lack of convincing use-cases; so
I see no point in going to the effort of providing a switch.

Note that 2 and 3 are actually the same thing (if you think they are
not, then you are putting the behavior in the wrong place).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-05-03 17:17:34 Re: [COMMITTERS] pgsql: Sigh ...
Previous Message Andrew Dunstan 2008-05-03 13:50:30 statement timeout vs dump/restore