Nah. I rebuilt the database from scratch on 2.0, so that seems unlikely. It segfaults when I create a fresh db and try to load postgis.sql. no data in the db yet.
--jlg -----Original Message----- From: postgis-users-boun...@postgis.refractions.net [mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Paul Ramsey Sent: Friday, May 11, 2012 2:22 AM To: PostGIS Users Discussion Subject: Re: [postgis-users] segmentation fault My bet: You've compiled and installed postgis2.0 on top of a postgis1.5 database. That is, you haven't re-loaded your data, you're trying to use your old data with the new code. That would probably cause segfaults on simple things like object access. P. On Thu, May 10, 2012 at 10:06 PM, Gold, Jack L (US SSA) <jack.g...@baesystems.com> wrote: > It appears it is the postgis-2.0.so library that is causing the > problem. I removed all but one call the library and it still > occurred. I tried some basic queries with no problem. I'll have to go back > to my compilation. > > > > --Jack Gold > > > > From: postgis-users-boun...@postgis.refractions.net > [mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of > Gold, Jack L (US SSA) > Sent: Thursday, May 10, 2012 4:53 PM > To: PostGIS Users Discussion (postgis-users@postgis.refractions.net) > Subject: [postgis-users] segmentation fault > > > > I'm trying to rebuild my i386(RHEL5) database (PostGIS-2.0.1SVN) on > x86_64 (CentOS). I've managed to build all of the libraries and I > believe they are all installed correctly, but when I attempt to load > postgis.sql, I get a seg-fault and the postmaster restarts wth: > > > > .LANGUAGE 'plpgsql' IMMUTABLE STRICT; > > ERROR: current transaction is aborted, commands ignored until end of > transaction block > > STATEMENT: CREATE OR REPLACE FUNCTION _ST_AsX3D(int4, geometry, int4, > int4, > text) > > RETURNS TEXT > > AS '$libdir/postgis-2.0','LWGEOM_asX3D' > > LANGUAGE 'C' IMMUTABLE; > > ERROR: current transaction is aborted, commands ignored until end of > transaction block > > STATEMENT: CREATE OR REPLACE FUNCTION ST_AsX3D(geom geometry, > maxdecimaldigits integer DEFAULT 15, options integer DEFAULT 0) > > RETURNS TEXT > > AS $$SELECT _ST_AsX3D(3,$1,$2,$3,'');$$ > > LANGUAGE 'sql' IMMUTABLE; > > LOG: received fast shutdown request > > LOG: aborting any active transactions > > LOG: autovacuum launcher shutting down > > LOG: shutting down > > LOG: database system is shut down > > LOG: database system was shut down at 2012-05-10 20:42:21 UTC > > LOG: autovacuum launcher started > > LOG: database system is ready to accept connections > > LOG: server process (PID 8543) 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-05-10 > 20:42:22 UTC > > LOG: database system was not properly shut down; automatic recovery > in progress > > LOG: record with zero length at 0/2A9A0F0 > > LOG: redo is not required > > LOG: autovacuum launcher started > > LOG: database system is ready to accept connections > > LOG: server process (PID 8572) 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-05-10 > 20:42:28 UTC > > LOG: database system was not properly shut down; automatic recovery > in progress > > LOG: record with zero length at 0/2A9A148 > > LOG: redo is not required > > LOG: autovacuum launcher started > > LOG: database system is ready to accept connections > > LOG: server process (PID 8581) 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-05-10 > 20:42:33 UTC > > LOG: database system was not properly shut down; automatic recovery > in progress > > LOG: record with zero length at 0/2A9A1A0 > > LOG: redo is not required > > LOG: autovacuum launcher started > > LOG: database system is ready to accept connections > > > > I'm looking around for more detail, but I'm not seeing anything. Any > ideas where I should look next? > > > > --Jack Gold > > > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users > _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
