| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Japin Li <japinli(at)hotmail(dot)com> |
| Cc: | mjurca(at)centrum(dot)cz, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17610: Use of multiple composite types incompatible with record-typed function parameter |
| Date: | 2022-09-16 17:28:02 |
| Message-ID: | 3841530.1663349282@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Japin Li <japinli(at)hotmail(dot)com> writes:
> On Fri, 09 Sep 2022 at 02:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So really the way we ought to fix this is to upgrade the parser
>> APIs so that plpgsql could deal with "$1.f1" as a unit. But
>> that seems like a lot of work, and it would certainly not be
>> back-patchable.
> Tested and looks good!
After letting this bake awhile, I still haven't thought of a better
idea. Also, even if we wanted to invest the effort to make "$1.f1"
an integrated construct, I think you could still easily break it,
say with syntax like "($1).f1". The variant "(arg).f1" would be
problematic too without this change.
Hence, pushed as-is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 大坏蛋！ | 2022-09-17 06:38:15 | error: #error PostgreSQL does not have native spinlock support on this platform. error: unknown type name ‘slock_t’ |
| Previous Message | Tom Lane | 2022-09-16 16:06:07 | Re: BUG #17615: Getting error while inserting records in the table: invalid byte sequence for encoding "UTF8": 0xae |