[postgis-users] GiST index on Geometry Column

[Kyle Wilcox]

Updating the PostGIS 1.3.2 solved the problem, thanks Mark.

Upgrading was surprisingly easy.

Kyle Wilcox wrote:
> I am indeed running PostGIS 1.1.6.
> 
> # select postgis_full_version();
> 
> postgis_full_version
> ----------------------------------------------------------------------------------
>  POSTGIS="1.1.6" GEOS="2.2.3-CAPI-1.1.1" PROJ="Rel. 4.5.0, 22 Oct 2006"
> USE_STATS
> (1 row)
> 
> 
> 
> # select * from pg_proc where proname='transform'
> 
> proname  | pronamespace | proowner | prolang | proisagg | prosecdef |
> proisstrict | proretset | provolatile | pronargs | prorettype |
> proargtypes | proallargtypes | proargmodes | proargnames |  prosrc   |
>       probin         | proacl
> -----------+--------------+----------+---------+----------+-----------+-------------+-----------+-------------+----------+------------+-------------+----------------+-------------+-------------+-----------+-----------------------+--------
>  transform |         2200 |       10 |      13 | f        | f         |
> t           | f         | i           |        2 |      16426 |    16426
> 23 |                |             |             | transform |
> $libdir/liblwgeom.dll |
> (1 row)
> 
> 
> I have not attempted to upgrade in the past but I may now take the step
> to get rid of the packaged PostGIS that came with Postgres and start
> using the Installers from refractions website.
> 
> Mark Cave-Ayland wrote:
>> On Thu, 2007-12-13 at 11:14 -0500, Kyle Wilcox wrote:
>>> I am having trouble creating a GiST index on a MULTIPOLYGON column.
>>> When the table is empty, the indexes will be created without errors, but
>>> inserts will fail with the error.  When the table has entries in it, the
>>> creation of the index will fail with the same error.  The index creation
>>> only fails on the poly_geom column and works in both conditions for the
>>> point_geom column.
>>>
>>> ERROR: function 60821C60 returned NULL
>>>
>>> PostgreSQL: 8.2.4 on Windows
>>
>> Hi Kyle,
>>
>> Could this be the indexing bug which caused the release of PostGIS
>> 1.1.7? What does "SELECT postgis_full_version();" and "select * from
>> pg_proc where proname = 'transform';" return?
>>
>> Also, have you attempted to upgrade PostGIS from 1.1.6 to 1.1.7 in the
>> past?
>>
>>
>> Kind regards,
>>
>> Mark.
>>
> 

-- 

 Kyle Wilcox
 NOAA Chesapeake Bay Office
 410 Severn Avenue
 Suite 107A
 Annapolis, MD 21403
 office: (410) 295-3151
 Kyle.Wilcox at noaa.gov

 "It is from the wellspring of our despair and the places
  that we are broken that we come to repair the world."
						- Murray Waas