Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout

On Wed, 16 Apr 2008 18:50:28 -0400
Andrew Dunstan <andrew@dunslane.net> wrote:

> 
> 
> 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.

That is an interesting idea. Something like:

pg_restore -E "SET STATEMENT_TIMEOUT=0; SET MAINTENANCE_WORK_MEM=1G" ?

Sincerely,

Joshua D. Drake

> 
> cheers
> 
> andrew
> 


-- 
The PostgreSQL Company since 1997: http://www.commandprompt.com/ 
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate