Skip site navigation (1) Skip section navigation (2)

pgsql: Fix behavior when raising plpy.Fatal()

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix behavior when raising plpy.Fatal()
Date: 2011-03-07 21:53:09
Message-ID: E1PwiMX-0006wz-6V@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Fix behavior when raising plpy.Fatal()

It should cause a elog(FATAL) error, and it fact it was simply causing
a elog(ERROR).

Jan UrbaƄski

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/804d13adfd2f66c70d8d95a606dde621b3213179

Modified Files
--------------
src/pl/plpython/plpython.c |    9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)

pgsql-committers by date

Next:From: Jaime CasanovaDate: 2011-03-08 00:20:27
Subject: Re: pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,
Previous:From: Tom LaneDate: 2011-03-07 21:21:54
Subject: pgsql: Improve description of inquiry functions that accept regclass.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group