Re: [PG19] Bogus errors for polymorphic plpython functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PG19] Bogus errors for polymorphic plpython functions
Date: 2026-10-31 03:41:32
Message-ID: 2928361.1793418092@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

shihao zhong <zhong950419(at)gmail(dot)com> writes:
> One thing. The patch rejects every pseudotype for OUT and TABLE
> arguments, including record. The old code skipped OUT arguments, and
> plpgsql does allow record there. Is that intended?

It is tighter than before. At least for polymorphic types, I don't
think the difference matters, because the core code will enforce that
you can't have a polymorphic output without a polymorphic input, so
we'd reject the function anyway. But maybe we should allow a RECORD
output; did that work before? (I'd bet not, but haven't tested)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mahendrakar Srinivasarao 2026-10-31 03:47:29 [PATCH] doc: Fix description of relative extension "directory" setting
Previous Message shihao zhong 2026-10-31 03:37:25 Re: [PG19] Bogus errors for polymorphic plpython functions