From: | Chapman Flack <jcflack(at)acm(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
Subject: | Re: FmgrInfo allocation patterns (and PL handling as staged programming) |
Date: | 2025-04-07 00:41:04 |
Message-ID: | 67F31F20.6090706@acm.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/06/25 20:01, Tom Lane wrote:
> Looking more closely at ProcedureCreate(), it makes a dependency
> if a transform *exists* for the argument or result type, whether
> a TRANSFORM clause is present or not. Surely this is completely
> bogus? We should be depending on the OIDs mentioned in protrftypes,
I think that's it. I tested by creating a function like
create function foo() returns text transform for type circle
that is, with the transform type not appearing as an argument or
return type.
As far as I know, that's still a cromulent usage, as I could be saying
I want the function to apply that transform to circles it uses or retrieves
in queries it makes.
But if the dependency is being created based on argument/return types
and not on protrftypes, that will slip right through the cracks.
Regards,
-Chap
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2025-04-07 00:43:39 | Re: Possibly hard-to-read message |
Previous Message | Fujii Masao | 2025-04-07 00:32:21 | Re: Use XLOG_CONTROL_FILE macro everywhere? |