Re: problems on Solaris - Mailing list pgsql-hackers

From Dave Page
Subject Re: problems on Solaris
Date
Msg-id CA+OCxozYAdpYf=QLNdx3x_4xpc7g9rXbp9RJE2zxuKEJ2DnL=A@mail.gmail.com
Whole thread Raw
In response to Re: problems on Solaris  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, May 25, 2015 at 1:07 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2015-05-24 19:44:37 -0400, Andrew Dunstan wrote:
>>
>> Buildfarm members casteroides and protosciurus have been having some
>> problems that seem puzzling. These animals both run on the same machine, but
>> with different compilers.
>>
>> casteroides runs with the Sun Studio 12 compiler, and has twice in the last
>> 3 days demonstrated this error:
>>
>>    [5561ce0c.51b7:25] LOG:  starting background worker process "test_shm_mq"
>>    [5561ce1e.5287:9] PANIC:  stuck spinlock (100cb77f4) detected at atomics.c:30
>>    [5561ce1e.5287:10] STATEMENT:  SELECT test_shm_mq_pipelined(16384, (select string_agg(chr(32+(random()*95)::int),
'')from generate_series(1,270000)), 200, 3); 
>>    [5561ce0c.51b7:26] LOG:  server process (PID 21127) was terminated by signal 6
>>    [5561ce0c.51b7:27] DETAIL:  Failed process was running: SELECT test_shm_mq_pipelined(16384, (select
string_agg(chr(32+(random()*95)::int),'') from generate_series(1,270000)), 200, 3); 
>>    [5561ce0c.51b7:28] LOG:  terminating any other active server processes
>>
>> It's not constant - between the two failures was a success.
>
> That's indeed rather odd. For one the relevant code does nothing but
> lock/unlock a spinlock. For another, there's been no recent change to
> this and casteroides has been running happily for a long time.
>
>> protociurus runs with gcc 3.4.3 and gets this error:
>>
>>    gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels
-Wmissing-format-attribute-Wformat-security -fno-strict-aliasing -fwrapv -Wno-unused-command-line-argument -g
-I/usr/local/include-m64 -I. -I../../../src/interfaces/libpq -I./../regress -I../../../src/include   -c -o specparse.o
specparse.c
>>    In file included from /usr/include/sys/vnode.h:47,
>>                      from /usr/include/sys/stream.h:22,
>>                      from /usr/include/netinet/in.h:66,
>>                      from /usr/include/netdb.h:98,
>>                      from ../../../src/include/port.h:17,
>>                      from ../../../src/include/c.h:1114,
>>                      from ../../../src/include/postgres_fe.h:25,
>>                      from specparse.y:13:
>>    /usr/include/sys/kstat.h:439: error: syntax error before numeric constant
>>    /usr/include/sys/kstat.h:463: error: syntax error before '}' token
>>    /usr/include/sys/kstat.h:464: error: syntax error before '}' token
>>    In file included from /usr/include/sys/stream.h:22,
>>                      from /usr/include/netinet/in.h:66,
>>                      from /usr/include/netdb.h:98,
>>                      from ../../../src/include/port.h:17,
>>                      from ../../../src/include/c.h:1114,
>>                      from ../../../src/include/postgres_fe.h:25,
>>                      from specparse.y:13:
>>    /usr/include/sys/vnode.h:105: error: syntax error before "kstat_named_t"
>
> I'd noticed this one as well. This sounds like a installation problem,
> not really ours. Dave, any chance you could look into this, or give
> somebody an account to test what's up?

I'm not going to be able to look at this, at least this week. I can
give someone on the EDB team access - Robert; can one of your guys
take a look?

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Naoya Anzai
Date:
Subject: Why does txid_current() assign new transaction-id?
Next
From: Albe Laurenz
Date:
Subject: Re: 9.5 release notes may need ON CONFLICT DO NOTHING compatibility notice for FDW authors