Re: anole: assorted stability problems

On Sun, Jun 28, 2015 at 7:27 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'd hoped that commit 1b468a131bd260c9041484f78b8580c7f232d580 would
> resolve this, but nope, anole is still getting occasional stuck spinlocks:
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2015-06-28%2021%3A35%3A02

That sucks.  It was easy to see that the old fallback barrier
implementation wasn't re-entrant, but this one should be.  And now
that I look at it again, doesn't the failure message indicate that's
not the problem anyway?

! PANIC:  stuck spinlock (c00000000d6f4140) detected at lwlock.c:816
! PANIC:  stuck spinlock (c00000000d72f6e0) detected at lwlock.c:770

That's just a straight-up SpinLockAcquire(), not a barrier call.

The May 5th failure looked like this:

! FATAL:  semop(id=0) failed: Result too large

The May 1st failure seems to have died here:

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company