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
unfa
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
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
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
> > 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)
> >
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 (y
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 (yes/no/defa
