Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Борис Мурашов <murasovb(at)gmail(dot)com>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-
Date: 2026-11-16 22:46:17
Message-ID: 266210.1794869177@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?UTF-8?B?0JHQvtGA0LjRgSDQnNGD0YDQsNGI0L7Qsg==?= <murasovb(at)gmail(dot)com> writes:
> One request from the user side: the new error "cannot cast type record to
> t" does not help much here. The function body looks correct, and the same
> query works as a plain SELECT, so it is not clear what to change. Is it
> possible to add an errhint() that tells the user to cast the row
> explicitly, for example "Cast the row value to type t explicitly"? This
> hint shows users the s::t workaround at once.

Okay, more or less as attached then.

regards, tom lane

Attachment Content-Type Size
draft-fix-coerce_record_to_complex.patch text/x-diff 6.3 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2026-11-16 22:53:49 Re: BUG #19903: ALTER COLUMN TYPE: "unexpected object depending on column" internal error via partition key
Previous Message Andres Freund 2026-11-16 22:39:28 Re: 16.16: join order regression for pg_indexes self-join (schema filter applied last), ~50x slower than 16.15