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

From: "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PL/pgSQL Todo, better information in errcontext from plpgsql
Date: 2006-10-05 12:20:29
Message-ID: BAY20-F181FF3A9791E842667C60CF9120@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>Hi, Tom,
>
>Tom Lane wrote:
>
> >> I miss some info in context: function's oid, function's argumenst and
> >> schema. Maybe:
> >
> >> 199292 function public.foo(int, int, int) language plpgsql statement
>return
> >> line 10
> >
> > Putting the OID there is a seriously awful idea, not least because it
> > would make it impossible to have stable regression-test outputs.
> >
> > I'm not really convinced that we need more than the function name.
>
>I also think that the OID will hurt here, but schema and argument types
>may be useful in some corner cases.
>

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.

Regards
Pavel Stehule

_________________________________________________________________
Emotikony a pozadi programu MSN Messenger ozivi vasi konverzaci.
http://messenger.msn.cz/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2006-10-05 12:52:34 Re: pgindent has been run
Previous Message Lukas Kahwe Smith 2006-10-05 12:05:32 Re: 8.2 beta blockers