Re: Bug in plpython's Python Generators

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jean-Baptiste Quenot <jbq(at)caraldi(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in plpython's Python Generators
Date: 2010-11-14 18:07:44
Message-ID: AANLkTi=Ai6dioMPWaBcZCoRWkMgF4Gq=uQCaX9NL1UrG@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 24, 2010 at 01:32, Jan Urbański <wulczer(at)wulczer(dot)org> wrote:
> The error handling in plpython is well-known to be a mess, hence the
> confusing error message that OP got. Another annoying thing is that SPI
> calls are not done in a subtransaction, which means you can't trap
> errors with a try/catch Python construct. I'm currently trying to get
> try/catch to work and might end up cleaning up error handling as well...
> but this can take me some time, so maybe someone should plug this
> particular hole right away.

While on this topic, maybe you can chime in on the pgsql-docs list for
my documentation patches to document the current (broken) behavior?

Regards,
Marti

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-11-14 18:12:32 Re: HOT updates in index-less tables
Previous Message Marko Tiikkaja 2010-11-14 18:07:22 Re: wCTE behaviour