[postgis-users] Crash when creating index on ( int, geom )

[Robin Chauhan]

I have items table with:

 item_pool    | integer                     | not null default '-1'
 item_geom  | geometry                 |
 
Indexing (item_geom, item_pool) works:

create index item_pool_index on items using gist ( item_geom
gist_geometry_ops, item_pool );
CREATE INDEX

But indexing in the opposite order does not (and crashes the server):

create index item_pool_index2 on trips using gist ( item_pool,
item_geom gist_geometry_ops );
 server closed the connection unexpectedly
 This probably means the server terminated abnormally

My system:

cp_test=# select postgis_version();
            postgis_version
---------------------------------------
 0.9 USE_GEOS=0 USE_PROJ=0 USE_STATS=1
cp_test=# select version();
                               version
---------------------------------------------------------------------
 PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC egcs-2.91.66
(1 row)

I have also installed contrib/btree_gist

Is this known behaviour?  Should I be able to index ( integer, geom )?  

The effect I want is that the performance of spatial queries for items
(which are points) in one pool, are not affected much by the how many
items there are in other pools.

Thanks!
-Robin Chauhan