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

From Pavel Stehule
Subject Re: proposal: better support for debugging of overloaded functions
Date
Msg-id CAFj8pRCWFhtYBHXzGFvz6yznzRog2RFT_K5PXc0cTP9PjDmm+w@mail.gmail.com
Whole thread Raw
In response to Re: proposal: better support for debugging of overloaded functions  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: proposal: better support for debugging of overloaded functions  (Abhijit Menon-Sen <ams@toroid.org>)
List pgsql-hackers
Hello

2011/11/21 Robert Haas <robertmhaas@gmail.com>:
> 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.

I inclined so this is good solution

there is a VIP patch

patch is relative long, but almost all are changes in regress tests.
Changes in plpgsql are 5 lines

Regards

Pavel


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

Attachment

pgsql-hackers by date:

Previous
From: Theo Schlossnagle
Date:
Subject: Re: logging in high performance systems.
Next
From: Tom Lane
Date:
Subject: Re: Making TEXT NUL-transparent