Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
От | Alvaro Herrera |
---|---|
Тема | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
Дата | |
Msg-id | 20080416225449.GH7942@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout ("Joshua D. Drake" <jd@commandprompt.com>) |
Ответы |
Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
|
Список | pgsql-hackers |
Joshua D. Drake escribió: > On Wed, 16 Apr 2008 18:50:28 -0400 > Andrew Dunstan <andrew@dunslane.net> wrote: > > Actually, it's probably more important to be selectable at restore > > time than at dump time, so if you're doing just one ... I think the patch posted by Joshua at the start of this thread does that. > > 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. > > That is an interesting idea. Something like: > > pg_restore -E "SET STATEMENT_TIMEOUT=0; SET MAINTENANCE_WORK_MEM=1G" ? We already have it -- it's called PGOPTIONS. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: