Re: statement timeout vs dump/restore

> > Do we want the following:
>=20
> > 1. pg_dump issues "set statement_timeout =3D 0;" to the=20
> database prior to=20
> > taking its copy of data (yes/no/default-but-switchable)
> > 2. pg_dump/pg_restore issue "set statement_timeout =3D 0;" in=20
> text mode=20
> > output (yes/no/default-but-switchable)
> > 3. pg_restore issues "set statement_timeout =3D 0;" to the=20
> database in=20
> > restore mode (yes/no/default-but-switchable)
>=20
> 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.
>=20
> 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).

I thought a proper fix for 3 would not depend on 2 ?

Andreas

--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers