From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: mismatching proargtypes/proallargtypes (bug #10122) |
Date: | 2014-04-24 01:26:47 |
Message-ID: | 15349.1398302807@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>>> 'trinque' on irc reported that "SELECT pg_catalog.pg_identify_object(oid,
>>> integer, integer)'::regprocedure" doesn't work and Andrew Gierth noticed
>>> it's because proargtypes doesn't match proallargtypes.
>> Ugh, how annoying.
> Argh!
On reflection it's not quite as bad as it seems: the correct signature of
the function is pg_identify_object(oid,oid,integer) and the regprocedure
code does accept that. AFAICT the only readily visible effect of the bug
is that psql's \df lies about what the input argument datatypes are.
> Maybe we can provide an UPDATE to fix it in existing installations, for
> those interested in doing so.
Doubt it's worth the trouble really ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-04-24 01:30:39 | Re: BUG #10122: proargtypes and proallargtypes are inconsistent for pg_identify_object |
Previous Message | Alvaro Herrera | 2014-04-24 01:06:00 | Re: mismatching proargtypes/proallargtypes (bug #10122) |