| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | udmcwher(at)mcs(dot)drexel(dot)edu |
| Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GiST indexing problems... |
| Date: | 2001-05-05 14:52:23 |
| Message-ID: | 5487.989074343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David McWherter <udmcwher(at)mcs(dot)drexel(dot)edu> writes:
> I've tried adding the parameters 'restrict = eqsel' and 'join = eqjoinsel'
> to the datatype operators, but that doesn't seem to change anything.
You might have better luck if you use area-related selectivity
estimators. Your problem seems to be that the optimizer doesn't
think the index is worth using, and the cause almost certainly is
overly pessimistic selectivity estimates for the indexable operators.
areasel and friends are completely bogus, but at least they deliver
small enough numbers to encourage use of the index ;-)
As Oleg says, the GiST support in 7.0.* is in pretty poor shape
(it had been suffering from neglect for a long time). Try 7.1.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David McWherter | 2001-05-05 15:20:20 | Re: GiST indexing problems... |
| Previous Message | Tom Lane | 2001-05-05 14:44:31 | Re: elog(LOG), elog(DEBUG) |