Re: polymorphic parameters limits - correct solution? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: polymorphic parameters limits - correct solution?
Date
Msg-id 20180116022144.6tw6cy26l5ddbhqv@alvherre.pgsql
Whole thread Raw
In response to polymorphic parameters limits - correct solution?  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: polymorphic parameters limits - correct solution?
List pgsql-hackers
Pavel Stehule wrote:
> Hi
> 
> I played with introduction of new pair of Polymorphic Parameters - like
> anyXelement and anyXarray. Now, I don't think so enhancing PP is good way
> now. Without significant redesign there are not practical append more code
> there.
> 
> Why this is a issue? The extension's authors are not able to specify result
> type without enumeration of all possible function signatures. Similar
> situation is in argument processing - there are workaround based on "any"
> type.

I cannot offer any advice for your "helper" (because I don't really
understand what the helper does), but I am reminded of this old thread:
https://www.postgresql.org/message-id/flat/20090908161210.GD549%40alvh.no-ip.org

... in which datatype "any" was one of the offered tools, and also from
whence the format() function sprung.  Nice ...

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] postgres_fdw bug in 9.6
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots