Re: PL/pgSQL Todo, better information in errcontext from plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PL/pgSQL Todo, better information in errcontext from plpgsql
Date: 2006-10-05 14:16:34
Message-ID: 12844.1160057794@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> writes:
> And what two variants of errcontext drived by GUC? First current
> (compatible) and second enhanced (with oid, params, maybe all possible debug
> values) and possible machine's readable. This enhanced variant can be
> compatible and shared in all environments.

[ shrug... ] The complaints I've heard about the errcontext mechanism
are that it's too verbose already. I can't see a good use-case for the
above, and I do know that a lot of people wouldn't consider it an
"enhancement" at all.

I suspect the problems you wish to solve would be better addressed by
using the plpgsql debugger that will be available with 8.2. It sounds
to me like you are wishing for a debugger stack trace, and if you need
one of those you probably need other debugger facilities too.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2006-10-05 14:30:53 Re: PL/pgSQL Todo, better information in errcontext from plpgsql
Previous Message Tom Lane 2006-10-05 13:46:47 Re: PL Caching in TopTransactionContext