On Wed, Apr 20, 2011 at 04:00:12PM +0200, Pavel Stehule wrote: > 2011/4/20 David Fetter <da...@fetter.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 <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
