ST_IsValid() causes termination of server connection
|Reported by:||blaggner||Owned by:||strk|
I have a polygon (see attachment) which always causes the termination of my server connection when I am trying to test it with ST_IsValid().
PostGIS: POSTGIS="1.5.2" GEOS="3.2.2-CAPI-1.6.2" PROJ="Rel. 4.7.1, 23 September 2009" LIBXML="2.7.3" USE_STATS (procs from 1.5 r5385 need upgrade)
PostgreSQL: PostgreSQL 8.4.5 on x86_64-unknown-linux-gnu, compiled by GCC gcc (SUSE Linux) 4.4.1 [gcc-4_4-branch revision 150839], 64-bit
(translated ) part of the pg_log error messages, related to this:
SELECT: IndexedNestedRingTester.cpp:71: bool geos::operation::valid::IndexedNestedRingTester::isNonNested(): assertion »innerRingPt!=null« not fulfilled.
2011-06-07 13:21:14 CEST LOG: Server process (PID 13483) was terminated by signal 6: Aborted
2011-06-07 13:21:14 CEST LOG: terminating any other active server processes
2011-06-07 13:21:14 CEST gis laggner_b WARNING: terminating connection because of crash of another server process
2011-06-07 13:21:14 CEST gis laggner_b DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2011-06-07 13:21:14 CEST gis laggner_b HINT: In a moment you should be able to reconnect to the database and repeat your command.
Additional comment from mike toews:
With a recent SVN version of PostGIS on PG 8.4 here is the moment before the crash:
NOTICE: [lwgeom.c:lwgeom_release:571] releasing type Polygon
NOTICE: [lwgeom.c:lwgeom_release:576] lwgeom_release: releasing bbox.
Change History (8)
comment:1 by , 12 years ago
|Milestone:||→ PostGIS 1.5.3|
|Priority:||medium → blocker|
|Version:||1.4.X → 1.5.X|