| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <greg(at)turnstep(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-17 06:20:50 |
| Message-ID: | 4806EC42.9000307@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Greg Sabino Mullane wrote:
>> I agree that we should do that, but the thread on -hackers ("Autovacuum
>> vs statement_timeout") wasn't totally conclusive. Greg Sabine Mullane
>> and Peter Eisentraut argued that we shouldn't, but neither provided a
>> plausible use case where a statement_timeout on restoring a dump would
>> be useful. I'm thinking we should apply the patch unless someone comes
>> up with one.
>
> I don't think it's fair to simply discard the use cases provided as
> "implausible" and demand one more to your liking.
Sorry if I missed it in the original thread, but what is the use case
you have in mind?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-04-17 06:31:32 | Re: MERGE SQL Statement |
| Previous Message | Heikki Linnakangas | 2008-04-17 06:11:12 | Re: Lessons from commit fest |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2008-04-17 08:48:42 | Re: printTable API (was: Show INHERIT in \du) |
| Previous Message | Bryce Nesbitt | 2008-04-17 04:12:47 | Re: Proposed patch - psql wraps at window width |