| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 13:19:21 |
| Message-ID: | BANLkTinaaZPiavc_VDp88Ozkdn2JvyauXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 20, 2011 at 2:33 AM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Sun, 2011-06-19 at 21:29 +0200, Florian Pflug wrote:
>> If I'm not mistaken about this, that would imply that we also cannot
>> have two range types with the same base type, the same opclass,
>> but different collations. Which seems rather unfortunate... In fact,
>> if that's true, maybe restricing range types to the database collation
>> would be best...
>
> 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. :-(
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-06-20 13:21:24 | Re: Re: patch review : Add ability to constrain backend temporary file space |
| Previous Message | Robert Haas | 2011-06-20 13:15:52 | Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault. |