[postgis-users] "make check" failures w/ 1.3.1 on Mac OS 10.5

[William Kyngesburye]

Well, for me at least, it appears that PostGIS built on Leopard is  
crashing Postgres.  Happens in both 32bit and 64bit modes.  I'm going  
to try my old PostGIS build (built on Tiger) with my new Postgres  
build, to help narrow it down (see if it's Postgres problem).

Here's what I get in the Postgres log:

STATEMENT:  SELECT AsKML(GeomFromEWKT('POINT(1 1)'));
LOG:  server process (PID 19619) was terminated by signal 10
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2007-11-25 15:29:20 CST
LOG:  checkpoint record is at 0/C99D88
LOG:  redo record is at 0/C99D88; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 0/3788; next OID: 32768
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system was not properly shut down; automatic recovery  
in progress
LOG:  record with zero length at 0/C99DD0
LOG:  redo is not required
LOG:  database system is ready

And in the Postgres crashlog:

Application Specific Information:
*** single-threaded process forked ***

Thread 0 Crashed:
0   libSystem.B.dylib             	0x900e1831 get_uint32 + 32
1   liblwgeom.so                  	0x0062ff6d lwcurve_deserialize + 125
2   liblwgeom.so                  	0x0061acfe parse_WKT_lwgeom + 142
3   postgres                      	0x000d6e75 ExecMakeFunctionResult +  
874
4   postgres                      	0x000d6a75 ExecEvalFuncArgs + 91
5   postgres                      	0x000d6b7b ExecMakeFunctionResult +  
112
6   postgres                      	0x000d76e8 ExecProject + 441
7   postgres                      	0x000e4553 ExecResult + 175
8   postgres                      	0x000d3e1c ExecProcNode + 216
9   postgres                      	0x000d269d ExecutorRun + 471
10  postgres                      	0x00160117 PortalRunSelect + 153
11  postgres                      	0x00161563 PortalRun + 625
12  postgres                      	0x0015c6b8 exec_simple_query + 1047
13  postgres                      	0x0015e5d1 PostgresMain + 6102
14  postgres                      	0x00135e91 ServerLoop + 3329
15  postgres                      	0x001375c7 PostmasterMain + 5061
16  postgres                      	0x000f461d main + 1378
17  postgres                      	0x000026ec _start + 210
18  postgres                      	0x00002619 start + 41

Thread 0 crashed with X86 Thread State (32-bit):
   eax: 0x00000009  ebx: 0x0062ff01  ecx: 0x0085ba75  edx: 0x00000005
   edi: 0x00000004  esi: 0x0085ba75  ebp: 0xbfffde18  esp: 0xbfffde18
    ss: 0x0000001f  efl: 0x00010207  eip: 0x900e1831   cs: 0x00000017
    ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
   cr2: 0x00000005

Fro 64bit mode, the thread state is:

Thread 0 crashed with X86 Thread State (64-bit):
   rax: 0x0000000000000006  rbx: 0x000000010082ba31  rcx:  
0x0000000000000020  rdx: 0x0000000000000002
   rdi: 0x000000010082ba31  rsi: 0x0000000000001790  rbp:  
0x00007fff5fbfdb10  rsp: 0x00007fff5fbfdb10
    r8: 0x0000000000000002   r9: 0x0000000000000001  r10:  
0x0000000100504220  r11: 0x00000001001c5627
   r12: 0x0000000000000000  r13: 0x000000010082ba30  r14:  
0x000000010082ba80  r15: 0x00000000000382fc
   rip: 0x00007fff8269ceea  rfl: 0x0000000000010283  cr2:  
0x0000000000000002


On Nov 25, 2007, at 2:19 PM, William Kyngesburye wrote:

> Possibly a permissions problem?  I just ran the tests on my new  
> Leopard build, using GEOS 3, and got 36/37 fails.
>
> Look in that /var/folders/... loader.err.  I got:
>
> BEGIN
> psql:/var/folders/sR/[snip]/-Tmp-/loader:2: NOTICE:  CREATE TABLE  
> will create implicit sequence "loadedshp_gid_seq" for serial column  
> "loadedshp.gid"
> psql:/var/folders/sR/[snip]/-Tmp-/loader:2: NOTICE:  CREATE TABLE /  
> PRIMARY KEY will create implicit index "loadedshp_pkey" for table  
> "loadedshp"
> CREATE TABLE
> psql:/var/folders/sR/[snip]/-Tmp-/loader:3: ERROR:  permission  
> denied for relation geometry_columns
> CONTEXT:  SQL statement "DELETE FROM geometry_columns WHERE
> 		f_table_catalog = '' AND f_table_schema = 'public' AND  
> f_table_name = 'loadedshp' AND f_geometry_column = 'the_geom'"
> PL/pgSQL function "addgeometrycolumn" line 94 at execute statement
> SQL statement "SELECT AddGeometryColumn('', $1 , $2 , $3 , $4 , $5 ,  
> $6 )"
> PL/pgSQL function "addgeometrycolumn" line 4 at SQL statement
>
> Even though I made my user role the owner of the postgis_reg  
> database, the lwpostgis.sql must be run as th postgres role, and it  
> gets ownership of the geometry_columns table.  And one big annoyance  
> I've had with postgres is that it doesn't inherit privileges like  
> you'd think.
>
> After setting up the postgis_reg DB for postgis, grant yourself all  
> privileges on the geometry_columns table.  After doing this, I now  
> get 32/37 fails - still a lot, but it's a start.

-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/

"Those people who most want to rule people are, ipso-facto, those  
least suited to do it."

- A rule of the universe, from the HitchHiker's Guide to the Galaxy