Re: Re: proposal - using names as primary names of plpgsql function parameters instead $ based names

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: proposal - using names as primary names of plpgsql function parameters instead $ based names
Date: 2017-05-19 01:14:17
Message-ID: 0cf239aa-91f0-b7ef-9a71-800b3ba1aa1a@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-05-19 01:17:53 Re: Getting error at the time of dropping subscription and few more issues
Previous Message Michael Paquier 2017-05-19 01:12:41 Re: [Proposal] Allow users to specify multiple tables in VACUUM commands