[postgis-users] Index on the Geomtery Column and GEOMETRYCOLLECTION EMPTY

Mark Cave-Ayland mark.cave-ayland at siriusit.co.uk
Thu Jul 8 02:37:52 PDT 2010

Sorin Dudui wrote:

> Hello,
> We have tables that contains both multi-polygons and empty geometries
> (MULTIPOLYGON EMPTY). The table has an index on the geometry column. After
> some updates with empty polygons the index becomes corrupt and we receive
> the error 
> "Relate Operation called with a LWGEOMCOLLECTION type.  This is unsupported
> when we make a spatial selection (ST_Intersects) with a polygon. ST_IsValid
> returns true for all geometries.
> If we delete the index the spatial query works without issues. For the
> moment our workaround is using permanent a  "not st_isEmpty) in the where
> clause. 
> Thank you,
> Sorin

Hi Sorin,

In order to debug this, we need much more information such as the 
versions of PostgreSQL/PostGIS you are using and a simple, reproducable 
test case.



Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
t: +44 870 608 0063

Sirius Labs: http://www.siriusit.co.uk/labs

More information about the postgis-users mailing list