Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names
Date
Msg-id 0cf239aa-91f0-b7ef-9a71-800b3ba1aa1a@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Re: proposal - using names as primary names of plpgsql functionparameters instead $ based names  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On 5/15/17 14:34, Pavel Stehule wrote:
>     Now, I when I working on plpgsql_check, I have to check function
>     parameters. I can use fn_vargargnos and out_param_varno for list of
>     arguments and related varno(s). when I detect some issue, I am using
>     refname. It is not too nice now, because these refnames are $ based.
>     Long names are alias only. There are not a possibility to find
>     related alias.
> 
>     So, my proposal. Now, we can use names as refname of parameter
>     variable. $ based name can be used as alias. From user perspective
>     there are not any change. 
> 
>     Comments, notes?
> 
> here is a patch

I don't understand what this is changing.  There are not documentation
or test changes.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Getting error at the time of dropping subscription andfew more issues