Re: pl/python tracebacks

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pl/python tracebacks
Date: 2011-02-24 13:10:01
Message-ID: 1298553001.4783.7.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shigeru HANADA 2011-02-24 13:13:15 Re: PostgreSQL FDW update
Previous Message Fujii Masao 2011-02-24 13:08:34 Re: Sync Rep v17