Opened 8 years ago

Closed 6 years ago

Last modified 3 years ago

#945 closed task (fixed)

expose and add selectivity to the 3d/4d index (&&&) bindings

Reported by: robe Owned by: pramsey
Priority: blocker Milestone: PostGIS 2.1.0
Component: postgis Version: trunk
Keywords: Cc:


How could you not ticket such an important feature :).

Change History (7)

comment:1 Changed 8 years ago by robe

Paul -- done with this? I know you've exposed it at the very least? Though haven't had a chance to stress test it.

comment:2 Changed 8 years ago by pramsey

No, this is still to be done, and a significant piece of work.

comment:3 Changed 7 years ago by strk

Milestone: PostGIS 2.0.0PostGIS 2.1.0

This one doesn't seem in time for 2.0. Probably shouldn't be blocker either.

comment:4 Changed 6 years ago by pramsey

Implementation here has also taken in aspects from #2101, to allow easier testing and verification of results. I'm quite happy with the constant selectivity estimates in my tests so far, and the join selectivity is if nothing else more sensitive to actual data distribution than before. All tests pass, including a couple tests for selectivity itself! (regress_selectivity.sql). r10796 on trunk

comment:5 Changed 6 years ago by pramsey

Hearing no issues, I declare this complete.

comment:6 Changed 6 years ago by pramsey

Resolution: fixed
Status: newclosed

comment:7 Changed 3 years ago by strk

This broke the NULL return from ST_Estimated_Extent, see #877 and #3396

Note: See TracTickets for help on using tickets.