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.geoghega...@gmail.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 > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
