| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: new polymorphic types - commontype and commontypearray |
| Date: | 2020-03-17 23:39:32 |
| Message-ID: | 32288.1584488372@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-03-18 00:07:10 | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |
| Previous Message | Justin Pryzby | 2020-03-17 23:32:18 | Re: Berserk Autovacuum (let's save next Mandrill) |