[postgis-users] Super weird problem: Cannot insert more than ~300 rows (or ~100 kb) into a table

[Nicolas Ribot]

> Ticket submitted:
>
>         http://trac.osgeo.org/postgis/ticket/1903
>
> But the crash problem seems not to happen for everyone. At least, the attached SQL file will crash my PostgreSQL 1.5.4 on Mac OS X 10.7.4 every time. But not for Paul. Would some of you be able to test it on your setup, to see if we can spot a pattern or connection? Thanks.
>

Hi,
Made some tests with different versions:
_____________________________________
Test 1: Pgis 1.5.3

                                      postgis_full_version
--------------------------------------------------------------------------------------------------
 POSTGIS="1.5.3" GEOS="3.3.2-CAPI-1.7.2" PROJ="Rel. 4.8.0, 6 March
2012" LIBXML="2.7.3" USE_STATS
(1 row)

Time: 16.980 ms
postgis15=# select version();

          version
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 PostgreSQL 9.1.1 on x86_64-apple-darwin11.1.0, compiled by
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
build 5658) (LLVM build 2335.15.00), 64-bit
(1 row)

=> Passed.


_____________________________________
Test 2:
Same Postgresql, postgis 2.0:
POSTGIS="2.0.0" GEOS="3.3.2-CAPI-1.7.2" PROJ="Rel. 4.8.0, 6 March
2012" LIBXML="2.7.3" USE_STATS (procs from 2.0 r7948 need upgrade)

=> passed
_____________________________________
Test 3: postgis 1.5.4
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

=> crashes:

server process (PID 11035) was terminated by signal 11: Segmentation fault
psql:/Users/nicolas/Downloads/test.sql:289: connection to server was lost
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted; last known up at 2012-07-10 14:02:44 CEST
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  consistent recovery state reached at 1E/92D6D278
LOG:  redo starts at 1E/92D6D278
LOG:  record with zero length at 1E/932A6558
LOG:  redo done at 1E/932A6518
LOG:  last completed transaction was at log time 2012-07-10 14:05:10.908316+02
LOG:  database system is ready to accept connections


Nicolas