| From: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
|---|---|
| To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: spgist index not getting used |
| Date: | 2014-09-25 00:36:08 |
| Message-ID: | etPan.5423637b.6b8b4567.13d2f@Crane.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Still no go. I actually tried a bunch of different selectivity functions too, and the planner correctly used them to estimate the number of potential returned functions, but in no case did the index actually kick in, no matter how selective I made the operator appear.
P.
--
http://postgis.net
http://cleverelephant.ca
On September 24, 2014 at 4:32:35 PM, Peter Geoghegan (peter(dot)geoghegan86(at)gmail(dot)com) wrote:
> On Wed, Sep 24, 2014 at 2:01 PM, Paul Ramsey wrote:
> > If I build an index on the same table using the internal quad-tree ops, and
> > use their operator, I do get an index scan.
>
>
> What about when enable_seqscan = off?
>
> --
> Regards,
> Peter Geoghegan
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-09-25 03:24:02 | Re: spgist index not getting used |
| Previous Message | Tatsuo Ishii | 2014-09-24 23:40:52 | Re: Synchronous replication + pgPool: not all transactions immediately visible on standby |