| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Fixing r-tree semantics |
| Date: | 2005-06-27 14:57:51 |
| Message-ID: | 20050627145751.GA18785@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 26, 2005 at 09:52:03 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Now that the module uses GIST instead of r-tree, there's no very strong
> reason why it should provide these operators at all. I propose removing
> all of << >> &< &> from contrib/cube, leaving only the four
> n-dimensional indexing operators (&& ~= ~ @).
>
> Any objections?
I seem to remember there being a problem if <, <=, > and >= operators
didn't exist and doing some operations (distinct or group by?) that
required sorting the data type. I am not sure that you are suggesting
that these operators be removed, as you didn't list them in either the
remove or keep list above.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-06-27 15:10:09 | For review: dbsize patch |
| Previous Message | Michael Fuhr | 2005-06-27 14:52:58 | Re: accessing postgres conf from stored procedure |