Re: problems on Solaris
От | Andrew Dunstan |
---|---|
Тема | Re: problems on Solaris |
Дата | |
Msg-id | 55627482.3020807@dunslane.net обсуждение исходный текст |
Ответ на | Re: problems on Solaris (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: problems on Solaris
|
Список | pgsql-hackers |
On 05/24/2015 08:07 PM, Andres Freund 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. > > Yes, but it wasn't running these tests until a few days ago when its buildfarm software was upgraded. cheers andrew
В списке pgsql-hackers по дате отправления: