From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dragos Valentin Moinescu <dragos.moinescu@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: plpythonu: how to catch plpy.execute() exceptions
Date: Fri, 29 Oct 2010 10:03:51 -0400
Message-ID: <671.1288361031@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTi=aaz=kv_08QH1tGPhK4b_Q1TwRk1tMbQX3fWVk@mail.gmail.com>
References: <AANLkTi=aaz=kv_08QH1tGPhK4b_Q1TwRk1tMbQX3fWVk@mail.gmail.com>
Dragos Valentin Moinescu <dragos.moinescu@gmail.com> writes:
> The thing is that I cannot catch the exception raised by plpy.execute().
Yeah, plpython's error handling is fundamentally broken. Somebody
needs to rewrite it to be more like the other PLs. In the meantime,
I'd suggest using plperl, which has gotten a lot more love than
plpython ever did.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, dragos.moinescu@gmail.com
Subject: Re: plpythonu: how to catch plpy.execute() exceptions
In-Reply-To: <671.1288361031@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox