| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com> |
| Subject: | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
| Date: | 2008-04-17 13:18:54 |
| Message-ID: | 200804171518.55929.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Heikki Linnakangas wrote:
> Sorry if I missed it in the original thread, but what is the use case
> you have in mind?
I think the bottom line is just that having statement_timeout a global setting
is stupid for a variety of reasons (dump, restore, vacuum, locks, incidental
delays) that we should discourage it (or prevent it, as proposed elsewhere)
rather than working around it in countless individual places.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-04-17 13:19:27 | Re: get rid of psql welcome message |
| Previous Message | Heikki Linnakangas | 2008-04-17 13:17:35 | Re: Re: [COMMITTERS] pgsql: Repair two places whereSIGTERM exit couldleave shared memory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-04-17 14:07:13 | Re: Proposed patch - psql wraps at window width |
| Previous Message | Peter Eisentraut | 2008-04-17 13:09:23 | Re: Proposed patch - psql wraps at window width |