From: | Walker Philips <wphilips53(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 21:20:45 |
Message-ID: | CAFssDwnKhGFcE2cXGo+9F1k-SuUTGRgSfzgDc_jsaQo-gMLhoA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PostgreSQL 14.4 (Ubuntu 14.4-1.pgdg22.04+1) on x86_64-pc-linux-gnu,
compiled by gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, 64-bit
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.
[image: image.png]
[image: image.png]
On Fri, Jul 15, 2022 at 7:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > Can you share which version of PostgreSQL you see this on?
>
> Hmm ... looking more closely, it's definitely not stock PG,
> because proargtypes is oidvector which would not include any
> curly braces in the output.
>
> Hard to tell what's going on exactly; seems like it could be
> corrupt catalog data or faulty code modifications. Or maybe
> there's something wrong with whatever the viewing tool is?
>
> regards, tom lane
>
--
Walker Philips
Data Engineering Consultant
Saguaro Capital Management
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-07-16 23:07:03 | Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty |
Previous Message | Tom Lane | 2022-07-16 00:54:58 | Re: pg_catalog.pg_proc procedure has correct proargnames array, but proargtypes is empty |