From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Darren Duncan <darren(at)darrenduncan(dot)net> |
Subject: | Re: Range Types and extensions |
Date: | 2011-06-20 14:17:23 |
Message-ID: | 24831.1308579443@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Jun 20, 2011 at 2:33 AM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>> Yes, we cannot have two range types with the same base type. That is a
>> consequence of the polymorphic type system, which needs to be able to
>> determine the range type given the base type.
> Boy, that's an unfortunate limitation. :-(
Given the need to deal with multiple collations for collatable types,
I'd say it's not so much "unfortunate" as "utterly unworkable". At
least unless you give up the notion of binding the collation into the
type definition ... which has other issues, per discussion a few days
ago. Even ignoring collations, I really think we want to allow multiple
range types for base types that have multiple btree sort orderings.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Radosław Smogura | 2011-06-20 14:39:01 | Re: POSIX question |
Previous Message | Florian Pflug | 2011-06-20 14:16:58 | Re: POSIX question |