| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench \for or similar loop |
| Date: | 2011-04-20 18:12:25 |
| Message-ID: | BANLkTi==WXG=1Oa1CZO0vEmL_UV3sk50ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 20, 2011 at 2:10 PM, David Fetter <david(at)fetter(dot)org> wrote:
> It is precisely this kind of issue that leads me to believe it would
> be counter-productive to come up with any client-specific hacks.
These definitional issues exist on the server, too, and weren't
considered early enough there either.
Preventing people from working on the things they care about is not a
good idea. There is no guarantee they will work on the things you
care about instead. They may just do nothing.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-04-20 18:13:36 | Re: pgindent weirdnessf |
| Previous Message | David Fetter | 2011-04-20 18:10:17 | Re: pgbench \for or similar loop |