Re: proposal: new polymorphic types - commontype and commontypearray
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>, Greg Stark <stark@mit.edu>,
David Steele <david@pgmasters.net>,
Robert Haas <robertmhaas@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2020-03-17T23:39:32Z
Lists: pgsql-hackers
I wrote: > Pavel Stehule <pavel.stehule@gmail.com> writes: >> There was a problem just with anyrange type. This last version looks >> perfect. > If you think that "matching polymorphic types" is too vague, I'm > not sure there's much daylight between there and spelling it out > in full as this latest patch does. "anyrange is the only problem" > might be a tenable viewpoint today, but once this patchset goes > in there's going to be much more scope for confusion about which > arguments potentially match a polymorphic result. On further reflection it seems like that's actually a fairly convincing argument for going with the more-verbose style. Hence, I pushed 0001 that way. The cfbot will be unhappy at this point, but I need to rebase the main patch again ... regards, tom lane
Commits
-
Introduce "anycompatible" family of polymorphic types.
- 24e2885ee304 13.0 landed
-
Refactor our checks for valid function and aggregate signatures.
- e6c178b5b73a 13.0 landed
-
Rearrange pseudotypes.c to get rid of duplicative code.
- 87c9c2571c81 13.0 landed