statement timeout vs dump/restore

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: statement timeout vs dump/restore
Date: 2008-05-03 13:50:30
Message-ID: 481C6DA6.80905@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


I'm a bit confused about where the consensus is on this issue (
http://archives.postgresql.org/message-id/20080311110727.62605f5f@commandprompt.com
et al)

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 would tend to say default-but-switchable for all 3, but maybe that's
too complicated.

cheers

andrew

Responses

Browse pgsql-hackers by date

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