From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench \for or similar loop |
Date: | 2011-04-20 16:12:00 |
Message-ID: | 20110420161200.GA17008@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 20, 2011 at 04:00:12PM +0200, Pavel Stehule wrote:
> 2011/4/20 David Fetter <david(at)fetter(dot)org>:
> > 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.
>
> then you need a real procedures that allows a explicit transaction
> handling. I am thinking so this task is feasible. We just need a
> implementation of CALL statement that runs a PL handler outside
> statement transaction. Probably some extension for PLPerl or PLPython
> can be more simple then PLpgSQL for begin.
>
> This is exactly task for "procedures"
Autonomous transactions allow for a broader scope than CALL in that
they do not require that we use a language other than SQL.
They'd make the CALL functionality a good deal easier to implement,
though.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-04-20 16:13:08 | Re: pgindent weirdness |
Previous Message | Tom Lane | 2011-04-20 16:04:16 | Re: pgindent weirdness |