"Pavel Stehule" <[EMAIL PROTECTED]> 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

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?


Reply via email to