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-16T00:20:49Z
Lists: pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes: > ne 15. 3. 2020 v 17:48 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal: >> Well, here's a version that does it like that, but personally I find these >> messages too verbose and not an improvement on what I had before. > 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. 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