From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Christopher Browne <cbbrowne(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
Subject: | Re: pgbench \for or similar loop |
Date: | 2011-04-19 17:30:37 |
Message-ID: | 201104191930.37770.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tuesday, April 19, 2011 07:22:54 PM Tom Lane wrote:
> I generally feel that such a feature would be better off done
> server-side --- after all, there's more clients in the world than psql
> and pgbench, and not all of them could use a C library even if we had
> one. But in either case the coding work is going to be dwarfed by the
> design work, if it's done right and not just the-first-hack-that-
> comes-to-mind.
On the other hand doing it client side stresses a different part of the code,
so it might be pretty sensible for pgbench...
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Aidan Van Dyk | 2011-04-19 17:33:31 | Re: pgbench \for or similar loop |
Previous Message | Alvaro Herrera | 2011-04-19 17:28:17 | Re: REINDEX vs broken HOT chains, redux |