| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(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:50:28 |
| Message-ID: | 480682B4.8080508@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-04-16 22:52:47 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
| Previous Message | Tom Lane | 2008-04-16 22:48:04 | Re: Lessons from commit fest |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-04-16 22:52:47 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
| Previous Message | Andrew Dunstan | 2008-04-16 22:40:05 | Re: Suppress compiler warnings on mingw |