Re: statement timeout vs dump/restore - Mailing list pgsql-hackers

From Zeugswetter Andreas OSB sIT
Subject Re: statement timeout vs dump/restore
Date
Msg-id E1539E0ED7043848906A8FF995BDA579030D41B6@m0143.s-mxs.net
Whole thread Raw
In response to Re: statement timeout vs dump/restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: statement timeout vs dump/restore  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
> > 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).

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

Andreas


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Query Hints? No thanks. Data hints?
Next
From: Andreas Pflug
Date:
Subject: Re: Proposed Patch - LDAPS support for servers on port 636 w/o TLS