Re: [HACKERS] statement timeout vs dump/restore

2008-05-06 Thread Robert Treat
On Monday 05 May 2008 09:01:25 Andrew Dunstan wrote: Zeugswetter Andreas OSB sIT wrote: 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

Re: [HACKERS] statement timeout vs dump/restore

2008-05-06 Thread Tom Lane
Robert Treat [EMAIL PROTECTED] writes: ISTR being unconvinced by the pg_restore arguments, but as I think about it some more, for someone to set statement_timeout on a production system, and then have that be blindly overridden by any random pg_dump user seems a bit unfair. pg_dump is not

Re: [HACKERS] statement timeout vs dump/restore

2008-05-06 Thread Andrew Dunstan
Tom Lane wrote: Robert Treat [EMAIL PROTECTED] writes: ISTR being unconvinced by the pg_restore arguments, but as I think about it some more, for someone to set statement_timeout on a production system, and then have that be blindly overridden by any random pg_dump user seems a bit

Re: [HACKERS] statement timeout vs dump/restore

2008-05-05 Thread Zeugswetter Andreas OSB sIT
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

Re: [HACKERS] statement timeout vs dump/restore

2008-05-05 Thread Andrew Dunstan
Zeugswetter Andreas OSB sIT wrote: 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

[HACKERS] statement timeout vs dump/restore

2008-05-03 Thread Andrew Dunstan
I'm a bit confused about where the consensus is on this issue ( http://archives.postgresql.org/message-id/[EMAIL PROTECTED] 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.

Re: [HACKERS] statement timeout vs dump/restore

2008-05-03 Thread Tom Lane
Andrew Dunstan [EMAIL PROTECTED] 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

Re: [HACKERS] statement timeout vs dump/restore

2008-05-03 Thread Joshua D. Drake
Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] 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