From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | 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 18:21:51 |
Message-ID: | 20080416112151.394bf479@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Wed, 16 Apr 2008 21:20:17 +0300
Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
> > My patch addresses all three, unless I am misunderstanding your
> > meaning. The patch does the following:
> >
> > After connection with pg_dump it executes set statement_timeout = 0;
> > This fixed the pg_dump timeout issue.
> >
> > It also writes set statement_timeout = 0 into the archive file,
> > which fixed pg_restore and psql.
>
> Oh, ok, I misread the patch. Sorry for the noise.
>
:)
Joshua D. Drake
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Browne | 2008-04-16 18:22:15 | Re: Lessons from commit fest |
Previous Message | Bryce Nesbitt | 2008-04-16 18:21:41 | Re: Commit fest queue |
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2008-04-16 21:19:55 | Re: [HACKERS] Text <-> C string |
Previous Message | Heikki Linnakangas | 2008-04-16 18:20:17 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |