"Sergey Konoplev" <[EMAIL PROTECTED]> writes:
> Could somebody explain me why it happens and how to make it work right?
Implement a selectivity estimator for <@ that isn't just a stub :-(
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.
>
> EXPLAIN ANALYZE of the query shows strange estimated rows count:
>
> EXPLAIN ANALYZE SELECT * FROM objonmap
> WHERE 1=1
>AND box(om_point, om_point) <@ box(point(-55.97398205077, -100),
> point(82.166446008477, 180))
>AND (om_flag OR om_ref_id IN (6901071, 6901513,
> 6901092
> run vacuum analyze ; before running that query, is it still off after
> that ?
>
I forgot to mention that ANALYZE, VACUUM ANALYZE even w/ FULL and
REINDEX doesn't help.
--
Regards,
Sergey Konoplev
--
PostgreSQL articles in english & russian
http://gray-hemp.blogspot.com/search/label/postgresql
run vacuum analyze ; before running that query, is it still off after
that ?
