Re: PL/pgSQL Todo, better information in errcontext from plpgsql
От | Pavel Stehule |
---|---|
Тема | Re: PL/pgSQL Todo, better information in errcontext from plpgsql |
Дата | |
Msg-id | BAY20-F181FF3A9791E842667C60CF9120@phx.gbl обсуждение исходный текст |
Ответ на | Re: PL/pgSQL Todo, better information in errcontext from (Markus Schaber <schabi@logix-tt.com>) |
Ответы |
Re: PL/pgSQL Todo, better information in errcontext from plpgsql
|
Список | 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/
В списке pgsql-hackers по дате отправления: