Hi,
I have a pl/perl trigger function which can give an error, and I would like to
catch it in a pl/pgsql function, but I can't seem to trap it.
Is it possible to catch errors generated pl/perl functions in a BEGIN ...
EXCEPTION WHEN ... END block? Or perhaps in some other way?
On Saturday 30 June 2007 23:14, Postgres User wrote:
> A basic question about raising exceptions in Postgres:
>
> If Function A calls Function B
>
> and Func B raises an exception, will the exception roll back the
> transaction in Func A by default? Or do I need to trap and re-raise
> the ex
On Saturday 30 June 2007 23:52, Postgres User wrote:
> How about this scenario:
>
> func A()
>
> begin
>x = func B();
>y = func C();
>
>z = func D();
>
> end
>
> Where func A, B, C, and D all update the db. If a funciton is raised
> in func D(), will all the transactions in t
On Sunday 01 July 2007 21:16, Michael Fuhr wrote:
> What have you tried and how did the outcome differ from your
> expectations?
The pl/perl trigger function in question generates an exception by
elog(ERROR, "message"). I also tried die(), which didn't make a difference.
When I do something on t
On Sunday 01 July 2007 21:50, Tom Lane wrote:
> Why would you expect it to? The raise_exception SQLSTATE applies
> specifically and solely to the plpgsql RAISE command. The entire
> point of those identifiers is to match fairly narrow classes of
> exceptions, not anything thrown by anyone.
>
>
On Thursday 24 May 2007 10:06, Jasbinder Singh Bali wrote:
> Hi
> I was wondering, apart from extensive procedural language support and being
> free,
> what are other major advantages of Postgresql over other major RDBMS like
> oracle and sql server.
>
> Any pointers would be highly appreciated.
On Thursday 24 May 2007 17:30, Alexander Staubo wrote:
> [2] Nobody else has this, I believe, except possibly Ingres and
> NonStop SQL. This means you can do a "begin transaction", then issue
> "create table", "alter table", etc. ad nauseum, and in the mean time
> concurrent transactions will just
