From: Tom Lane <tgl@sss.pgh.pa.us>
To: Walker Philips <wphilips53@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: pg_catalog.pg_proc procedure has correct proargnames array,
 but proargtypes is empty
In-reply-to: 
 <CAFssDw=Hs5i1VNAaafNdDdvMNCF0gh7f4x=D-Of1eUJDhGin5A@mail.gmail.com>
References: 
 <CAFssDw=Hs5i1VNAaafNdDdvMNCF0gh7f4x=D-Of1eUJDhGin5A@mail.gmail.com>
Comments: In-reply-to Walker Philips <wphilips53@gmail.com>
	message dated "Fri, 15 Jul 2022 18:37:47 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3546147.1657932327.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Jul 2022 20:45:27 -0400
Message-ID: <3546148.1657932327@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3546148.1657932327%40sss.pgh.pa.us>
Precedence: bulk

Walker Philips <wphilips53@gmail.com> writes:
> The following function's metadata is not correctly reported in the pg_pr=
oc
> table (see picture below).

Looks fine to me:

regression=3D# CREATE OR REPLACE FUNCTION get_period_type_adjustment(perio=
d_type_id =

integer)
 RETURNS numeric
...
regression=3D# \x
Expanded display is on.
regression=3D# select * from pg_proc where proname =3D 'get_period_type_ad=
justment';
...
pronargs        | 1
pronargdefaults | 0
prorettype      | 1700
proargtypes     | 23
proallargtypes  | =

proargmodes     | =

proargnames     | {period_type_id}
proargdefaults  | =

...

One IN integer argument named period_type_id, result type numeric.

Note the comments in

https://www.postgresql.org/docs/devel/catalog-pg-proc.html

that proallargtypes etc. are generally set to NULL if they wouldn't
carry any additional data.  This is a choice we made a long time
ago to prioritize storage space over simplicity of implementation.
I don't know whether we'd make the same choice in a green field
today ... but we're not going to change it now, because the ensuing
confusion would be pretty bad.

			regards, tom lane