Re: pl/python tracebacks

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>
To: Jan Urbański <wulczer@wulczer.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Postgres - Hackers <pgsql-hackers@postgresql.org>
Date: 2011-03-01T21:12:16Z
Lists: pgsql-hackers
On tis, 2011-03-01 at 21:10 +0100, Jan Urbański wrote:
> So you end up with a context message saying "PL/Python function %s"
> and a detail message with the saved detail (if it's present) *and* the
> traceback. The problem is that the name of the function is already in
> the traceback, so there's no need for the context *if* there's a
> traceback present.

I wouldn't actually worry about that bit of redundancy so much.  Getting
proper context for nested calls is much more important.