From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
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 14:00:12 |
Message-ID: | BANLkTinbUJj+_d+evQTEgggHLHnZ0Pn9OA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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"
Regards
Pavel
>
> 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 | Andrew Dunstan | 2011-04-20 14:02:18 | Re: Build farm coverage for isolation tests |
Previous Message | Tom Lane | 2011-04-20 13:59:11 | Re: Foreign table permissions and cloning |