Re: PL/pgSQL Todo, better information in errcontext from - Mailing list pgsql-hackers

From Markus Schaber
Subject Re: PL/pgSQL Todo, better information in errcontext from
Date
Msg-id 4523E724.2030705@logix-tt.com
Whole thread Raw
In response to Re: PL/pgSQL Todo, better information in errcontext from plpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PL/pgSQL Todo, better information in errcontext from plpgsql
List 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.

Markus

--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] qsort_arg needed for msvc build
Next
From: "Magnus Hagander"
Date:
Subject: Re: [PATCHES] qsort_arg needed for msvc build