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

From Pavel Stehule
Subject [HACKERS] Re: proposal - using names as primary names of plpgsql functionparameters instead $ based names
Date
Msg-id CAFj8pRDntU2nph=gqkMcdTXZ4x0hKOPA74-=d9ZvMQsCESVfsg@mail.gmail.com
Whole thread Raw
In response to [HACKERS] 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  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers


2017-05-13 18:26 GMT+02:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hi

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

Regards

Pavel
 

Regards

Pavel

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternative hosts when some errors occur
Next
From: Kevin Grittner
Date:
Subject: Re: [HACKERS] transition table behavior with inheritance appearsbroken (was: Declarative partitioning - another take)