Re: proposal: more practical view on function's source code - Mailing list pgsql-hackers

From Tom Lane
Subject Re: proposal: more practical view on function's source code
Date
Msg-id 22165.1269186166@sss.pgh.pa.us
Whole thread Raw
In response to Re: proposal: more practical view on function's source code  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: more practical view on function's source code
Re: proposal: more practical view on function's source code
Re: proposal: more practical view on function's source code
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> I understanding. But this functionality is implemented yet. My
> motivation is to design some tool for more easy searching n. row in
> source code (for interpretation error messages) and possibility to see
> this row in some context.

Why is this a good way to attack that?  If you think the context already
provided in error messages isn't good enough, seems like the thing to do
is fix the error messages.  Nobody is going to want to dump out a
multi-hundred-line function like this in order to identify which
statement is being fingered by an error.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: xmlconcat (was 9.0 release notes done)
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: more practical view on function's source code