Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Walker Philips <wphilips53(at)gmail(dot)com>
Cc: dgrowleyml(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty
Date: 2022-07-16 23:07:03
Message-ID: 4021741.1658012823@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Walker Philips <wphilips53(at)gmail(dot)com> writes:
> I'm using DBeaver as my IDE. The column does appear to be oidvector. Other
> functions seem to come through ok weirdly enough. It potentially might be a
> visual glitch with DBeaver based on the following screenshot. Still pretty
> odd. I can submit to DBeaver if that might be the underlying issue.

I'd try looking at the row in psql. If it looks normal there,
then it's a DBeaver problem.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2022-07-17 19:23:36 BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
Previous Message Walker Philips 2022-07-16 21:20:45 Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty