Excerpts from Robert Haas's message of mar abr 19 13:33:27 -0300 2011: > On Tue, Apr 19, 2011 at 12:27 PM, Christopher Browne <cbbro...@gmail.com> > wrote: > > On Tue, Apr 19, 2011 at 12:22 PM, Robert Haas <robertmh...@gmail.com> wrote: > >> Yeah. I was wondering if anyone was gung-ho enough about this to > >> implement some kind of library that both programs could draw on. > >> > >> It probably wouldn't be super-hard, if we could agree on a rough design. > > > > It seems to me that the Mo Betta answer would be to implement the > > fabled "stored procedure" language, that has, as its distinctive, the > > capability to control transactions. That would have the capability of > > being used in places other than just inside psql. > > > > And it would be a good way for scripting things like specialized > > vacuum and analyze regimens, which cannot be done inside stored > > functions today. > > 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. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
