Re: why does plperl cache functions using just a bool for is_trigger
From:
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:
Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
Cc:
Jan Urbański <wulczer(at)wulczer(dot)org>, Alex Hunsaker <badalex(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject:
Re: why does plperl cache functions using just a bool for is_trigger
Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
> Are you sure that having each try/except use a subtransaction is the
> right way to do it ?
Actually it is not: what you have to do is use a subtransaction in the
plpy.execute() operation, so that if the called SQL operation fails, you
can clean it up and then report the error to Python as if it were any
other Python error. Messing with the host language's exception handling
is a sure route to misery. plperl and pltcl both contain examples of
doing this properly.
regards, tom lane
