Opened 10 years ago

Closed 6 years ago

#2256 closed enhancement (fixed)

ST_EstimatedExtent bound to index

Reported by: pramsey Owned by: pramsey
Priority: medium Milestone: PostGIS 2.5.0
Component: postgis Version: 2.0.x
Keywords: Cc:


Where possible, read the head of the index to get an estimate of the spatial extent.

Change History (9)

comment:1 by robe, 10 years ago

Milestone: PostGIS 2.1.0PostGIS 2.2.0

if you can get this done by next week push back. if not — its gonna have to wait.

comment:2 by pramsey, 8 years ago

Milestone: PostGIS 2.2.0PostGIS 2.3.0

comment:3 by robe, 7 years ago

Milestone: PostGIS 2.3.0PostGIS 2.4.0

comment:4 by robe, 6 years ago

Milestone: PostGIS 2.4.0PostGIS 2.5.0

comment:5 by robe, 6 years ago

Milestone: PostGIS 2.5.0PostGIS 2.4.0

comment:6 by robe, 6 years ago

Milestone: PostGIS 2.4.0PostGIS 2.5.0

comment:7 by pramsey, 6 years ago

In 16149:

Proof of content for reading table extent from
the top of the index. Can be called with
_postgis_index_extent(tbl regclass, col text)
and returns box2d.

Currently not added to the st_estimatedextent()
code, because it has issues with indexes that
have EMPTY added to them. This is a symptom
of #2487. While it seems impossible to every
allow index-assisted searches for EMPTY
geometry, it will be necessary to create
invalid keys for them (NaN, NaN, NaN, Nan)
and then handle those keys so they don't
pollute the index with strange bounds.

References #2256

comment:8 by pramsey, 6 years ago

Updated empty keys to use NaN boxes in r16151, and added index read to ST_EstimatedExtent() code.

comment:9 by pramsey, 6 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.