Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Date
Msg-id 480682B4.8080508@dunslane.net
Whole thread Raw
In response to Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout  ("Alex Hunsaker" <badalex@gmail.com>)
Responses Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers

Alex Hunsaker wrote:
>
>
> Sorry if i missed the obvious reason not to do this... but if its a
> command line option the user can choose.  Why not something like this
> (i did it for pg_dump only...)
>
>
>   
Actually, it's probably more important to be selectable at restore time 
than at dump time, so if you're doing just one ...

This whole thing set me wondering whether or not we should provide a 
more general command-line facility to psql and pg_restore, and maybe 
others, to do some session setup before running their commands.

Of course, there's no reason we couldn't have both.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Lessons from commit fest
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout