Re: pgbench \for or similar loop - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgbench \for or similar loop
Date
Msg-id 5882.1303233774@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgbench \for or similar loop  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pgbench \for or similar loop  (Andres Freund <andres@anarazel.de>)
Re: pgbench \for or similar loop  (Aidan Van Dyk <aidan@highrise.ca>)
Re: pgbench \for or similar loop  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Robert Haas's message of mar abr 19 13:33:27 -0300 2011:
>> Well, I'm all good with that, too, but am not fired up about either
>> one to implement it myself.  So I think it's going to come down to
>> what the person doing the work feels most strongly about.

> I'm not at all fired up about stored procedures.  The \for pgbench
> feature I'm proposing is 2 orders of magnitude less code than that.

I think what that really translates to is "I don't want to bother doing
the careful design work that Robert talked about". -1 for that approach.

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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: REINDEX vs broken HOT chains, redux
Next
From: Alvaro Herrera
Date:
Subject: Re: REINDEX vs broken HOT chains, redux