MIME-Version: 1.0
References: <CAOzAquKPXRWp38u9cURDCd4XzKCbKLhuZvH6AQjtXGW3R6-LoQ@mail.gmail.com>
 <577338.1720304029@sss.pgh.pa.us> <CAFj8pRBcwQ3CVGj7eDFezhG-dUtrsry3T9iHf0SmEnU=YXs-LQ@mail.gmail.com>
 <CAFj8pRBZUNjmDXwByeSuE5H+vQGBDyn-AQg9-kRX4eKrAUqOCQ@mail.gmail.com>
 <CAOzAquK=sA1_PRVB3unA9uyByvSjVH3QMhd2Pjkxk_845sSPFg@mail.gmail.com>
 <CAFj8pRCMpZ-pn8v_U316X=rKvPCg1nbe+_aKpj0qPUGy8fiqfw@mail.gmail.com> <3f8781c5-d625-4f24-b96d-56a45a0dd257@aklaver.com>
In-Reply-To: <3f8781c5-d625-4f24-b96d-56a45a0dd257@aklaver.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
Date: Sun, 7 Jul 2024 16:53:24 +0200
Message-ID: <CAFj8pRDTn1GOy+QZGqUOrtyZHGfENNQTyBi-f8qesZ0JjXqPSg@mail.gmail.com>
Subject: Re: Declaring a field that is also an out parameter in a function
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Michael Nolan <htfoot@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, 
	"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000826d3f061ca97775"
Archived-At: <https://www.postgresql.org/message-id/CAFj8pRDTn1GOy%2BQZGqUOrtyZHGfENNQTyBi-f8qesZ0JjXqPSg%40mail.gmail.com>
Precedence: bulk

--000000000000826d3f061ca97775
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

ne 7. 7. 2024 v 16:48 odes=C3=ADlatel Adrian Klaver <adrian.klaver@aklaver.=
com>
napsal:

> On 7/7/24 07:42, Pavel Stehule wrote:
> >     I'm not sure why there's a warning about using an alias. 43.3.1 say=
s
> >     to use them for improved readability.
> >
> >
> > it is obsolete - aliases were used when Postgres doesn't support named
> > arguments.
>
> Is that was what it was complaining about or the fact they where
> declared and never used?
>

I am not sure if I understand the question. My  reply was related to
generic usage of aliases.

Report from plpgsql_check was correct - and related variables were not
used.


> >
> > I  don't know any good reason why one variable can use more than one
> name.
>
> Section 43.3.2. ALIAS provides the pros/cons.
>
> >
> > There can be an exception when argument names are very long, but
> > generally they are not used.
> >
> >
> >
> >     Mike Nolan
> >
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
>

--000000000000826d3f061ca97775
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">ne 7. 7. 2024 v=C2=A016:48 odes=C3=AD=
latel Adrian Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian=
.klaver@aklaver.com</a>&gt; napsal:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">On 7/7/24 07:42, Pavel Stehule wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0I&#39;m not sure why there&#39;s a warning about us=
ing an alias. 43.3.1 says<br>
&gt;=C2=A0 =C2=A0 =C2=A0to use them for improved readability.<br>
&gt; <br>
&gt; <br>
&gt; it is obsolete - aliases were used when Postgres doesn&#39;t support n=
amed <br>
&gt; arguments.<br>
<br>
Is that was what it was complaining about or the fact they where <br>
declared and never used?<br></blockquote><div><br></div><div>I am not sure =
if I understand the question. My=C2=A0 reply was related to generic usage o=
f aliases.</div><div><br></div><div>Report from plpgsql_check was correct -=
 and related variables were not used. <br></div><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">
<br>
&gt; <br>
&gt; I=C2=A0 don&#39;t know any good reason why one variable can use more t=
han one name.<br>
<br>
Section 43.3.2. ALIAS provides the pros/cons.<br>
<br>
&gt; <br>
&gt; There can be an exception when argument names are very long, but <br>
&gt; generally they are not used.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Mike Nolan<br>
&gt; <br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
<br>
</blockquote></div></div>

--000000000000826d3f061ca97775--