Re: proposal: better support for debugging of overloaded functions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: proposal: better support for debugging of overloaded functions
Date
Msg-id CA+TgmobO3PT8aRf3KZUQS_Uc0c_mKftXk=Fa=ueUETE0tqGF3g@mail.gmail.com
Whole thread Raw
In response to Re: proposal: better support for debugging of overloaded functions  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: better support for debugging of overloaded functions
List pgsql-hackers
On Sun, Nov 20, 2011 at 6:16 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> Is possible to add GUC variable plpgsql.log_function_signature (maybe
> just log_function_signature (for all PL))? I am not sure about GUC
> name.
>
> When this variable is true, then CONTEXT line will contain a qualified
> function's signature instead function name

Sure, but why?  If it's possible to do that, I think we should just do
it always.  It might be a net reduction in readability for people who
don't use overloading but do have functions with very long names and
lots and lots of arguments, but even if you think that's good design,
I think the general principle that an error message should uniquely
identify the object responsible for the error ought to take
precedence.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: psql \ir filename normalization
Next
From: Robert Haas
Date:
Subject: Re: EXPLAIN (plan off, rewrite off) for benchmarking