anole: assorted stability problems - Mailing list pgsql-hackers

From Alvaro Herrera
Subject anole: assorted stability problems
Date
Msg-id 20150520192157.GE5885@postgresql.org
Whole thread Raw
Responses Re: anole: assorted stability problems  (Andres Freund <andres@anarazel.de>)
Re: anole: assorted stability problems  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
In HEAD only.  Previous branches seem mostly clean, so there's something
going wrong.  Spinlocks going wrong perhaps?

http://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=anole&dt=2015-05-20%2016%3A30%3A26&stg=check
! PANIC:  stuck spinlock (c00000000d6f4140) detected at lwlock.c:816
! server closed the connection unexpectedly
!     This probably means the server terminated abnormally
!     before or while processing the request.
! connection to server was lost

http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2015-05-09%2020%3A30%3A29
! PANIC:  semop(id=0) failed: Result too large
! server closed the connection unexpectedly
!     This probably means the server terminated abnormally
!     before or while processing the request.
! connection to server was lost

http://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=anole&dt=2015-05-05%2018%3A39%3A38&stg=check
! FATAL:  semop(id=0) failed: File too large
! server closed the connection unexpectedly
!     This probably means the server terminated abnormally
!     before or while processing the request.
! connection to server was lost

http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2015-05-03%2012%3A30%3A18
! PANIC:  semop(id=-1073741824) failed: Invalid argument
! server closed the connection unexpectedly
!     This probably means the server terminated abnormally
!     before or while processing the request.
! connection to server was lost

http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2015-04-29%2004%3A30%3A25
! PANIC:  stuck spinlock (c00000000d335360) detected at lwlock.c:767
! server closed the connection unexpectedly
!     This probably means the server terminated abnormally
!     before or while processing the request.
! connection to server was lost

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: jsonb concatenate operator's semantics seem questionable
Next
From: Robert Haas
Date:
Subject: Re: RFC: Non-user-resettable SET SESSION AUTHORISATION