Re: pgbench \for or similar loop
От | Merlin Moncure |
---|---|
Тема | Re: pgbench \for or similar loop |
Дата | |
Msg-id | BANLkTik0fQrDcOxBwN5bKvDKgXO3Y06tjA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgbench \for or similar loop (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: pgbench \for or similar loop
|
Список | pgsql-hackers |
On Wed, Apr 20, 2011 at 9:14 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Excerpts from David Fetter's message of mié abr 20 10:54:56 -0300 2011: >> On Wed, Apr 20, 2011 at 08:05:07AM +0200, Pavel Stehule wrote: >> > Hello >> > >> > I played with psql extensions two years ago - it can do it >> >> It's interesting, but it doesn't solve the fundamental problem, which >> is to allow every client, not just psql, to do this. > > Why is this problem fundamental? I happen to like your idea, even if we had stored procedures...they have a lot of overlap but so what?. We have server side \copy and client side COPY -- both are useful. Likewise, (getting back to the original point of the thread), bechmarking via client scripting and via procedure are also both useful. Nobody will gripe if psql gets more features like this -- some people really want to do this on the client side and there are valid reasons to do that, say, to intermix client local shell commands between sql lines. merlin
В списке pgsql-hackers по дате отправления: