| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | d <dchuck(at)yurfish(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR: type of parameter 1 (fruit2) does not match that when preparing the plan (fruit1) |
| Date: | 2022-05-01 17:08:57 |
| Message-ID: | 1683365.1651424937@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sun, May 1, 2022 at 8:44 AM d <dchuck(at)yurfish(dot)com> wrote:
>> CREATE OR REPLACE FUNCTION record_to_form_data(p_r record)
> Not a bug, it is a documented limitation.
FWIW, it does seem to work as desired if you declare the argument as
"anyelement".
Maybe we could improve this situation by treating a "record" parameter
as polymorphic, though that might cause some odd inconsistencies with
plpgsql's historical treatment of "record" local variables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-05-01 19:34:43 | Re: ERROR: type of parameter 1 (fruit2) does not match that when preparing the plan (fruit1) |
| Previous Message | David G. Johnston | 2022-05-01 15:58:38 | Re: ERROR: type of parameter 1 (fruit2) does not match that when preparing the plan (fruit1) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2022-05-01 17:25:17 | Re: Missing can't-assign-to-constant checks in plpgsql |
| Previous Message | Justin Pryzby | 2022-05-01 16:52:09 | Re: testclient.exe installed under MSVC |