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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Alex Hunsaker <badalex(at)gmail(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Date: 2008-04-16 22:54:49
Message-ID: 20080416225449.GH7942@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Joshua D. Drake escribió:
> On Wed, 16 Apr 2008 18:50:28 -0400
> Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2008-04-16 23:02:06 Re: How to submit a patch
Previous Message Joshua D. Drake 2008-04-16 22:52:47 Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout

Browse pgsql-patches by date

  From Date Subject
Next Message Alex Hunsaker 2008-04-16 23:21:35 Re: [HACKERS] Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Previous Message Joshua D. Drake 2008-04-16 22:52:47 Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout