Re: pl/python tracebacks - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pl/python tracebacks
Date
Msg-id 1298553001.4783.7.camel@vanquo.pezone.net
Whole thread Raw
In response to pl/python tracebacks  (Jan Urbański <wulczer@wulczer.org>)
Responses Re: pl/python tracebacks  (Jan Urbański <wulczer@wulczer.org>)
List pgsql-hackers
On tor, 2010-12-23 at 14:56 +0100, Jan Urbański wrote:
> For errors originating from Python exceptions add the traceback as the
> message detail. The patch tries to mimick Python's traceback.py module
> behaviour as close as possible, icluding interleaving stack frames
> with source code lines in the detail message. Any Python developer
> should instantly recognize these kind of error reporting, it looks
> almost the same as an error in the interactive Python shell.

I think the traceback should go into the CONTEXT part of the error.  The
context message that's already there is now redundant with the
traceback.

You could even call errcontext() multiple times to build up the
traceback, but maybe that's not necessary.




pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Sync Rep v17
Next
From: Shigeru HANADA
Date:
Subject: Re: PostgreSQL FDW update