From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Paul Ramsey <pramsey(at)refractions(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GiST a second class citizen? |
Date: | 2002-12-02 01:55:06 |
Message-ID: | 3869.1038794106@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Paul Ramsey <pramsey(at)refractions(dot)net> writes:
> So far, GiST is integrated into the main tree, but all the bindings seem
> to be kept outside, in contrib (ltree, btree, rtree).
This is a historical artifact. As GiST comes more up-to-speed, the
operator classes for it should become mainstream.
> Would I be completely out-to-lunch if I suggested that the GiST
> bindings might even replace the standard ones?
Yes. There is no "replacement" involved here, because opclasses for
different index types are quite independent.
(Perhaps what you are really suggesting is that GiST should become the
default index type instead of btree --- to which I can only reply that
it's got a *long* way to go before that would be considered for an
instant...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-12-02 02:23:22 | Re: Read-only plan trees |
Previous Message | Paul Ramsey | 2002-12-02 01:43:23 | GiST a second class citizen? |