Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1904 closed defect (duplicate)

PostgreSQL crashes every time if I insert more than ~280 rows containing a GEOGRAPHY POINT in a table containing a GIST index

Reported by: renefournier Owned by: pramsey
Priority: critical Milestone: PostGIS 1.5.5
Component: postgis Version: 1.5.X
Keywords: postgis crash gist geography point Cc: renefournier@…

Description

Creating a table with a GIST index on the GEOGRAPHY(POINT,4326) column, and then inserting hundreds rows, PostgreSQL will crash every time at row 284 (changing the order of the rows will affect at which row the crash occurs — appears to be dependent on cumulative data size). If I remove the index, the crash never occurs.

postgis_full_version


POSTGIS="1.5.4" GEOS="3.3.2-CAPI-1.7.2" PROJ="Rel. 4.8.0, 6 March 2012" LIBXML="2.7.8" USE_STATS

Log output:

LOG: server process (PID 1373) was terminated by signal 11: Segmentation fault LOG: terminating any other active server processes WARNING: terminating connection because of crash of another server process 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. HINT: In a moment you should be able to reconnect to the database and repeat your command. LOG: all server processes terminated; reinitializing LOG: database system was interrupted; last known up at 2012-07-06 10:46:58 CEST LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 0/38E6268 LOG: record with zero length at 0/393AB08 LOG: redo done at 0/393AAC8 LOG: last completed transaction was at log time 2012-07-06 10:47:17.590389+02 LOG: database system is ready to accept connections LOG: autovacuum launcher started

Change History (3)

comment:1 by pramsey, 12 years ago

Resolution: duplicate
Status: newclosed

comment:2 by robe, 12 years ago

Milestone: PostGIS 1.5.4PostGIS 1.5.5

comment:3 by robe, 12 years ago

dupe of #1832 ?

Note: See TracTickets for help on using tickets.