Re: anole: assorted stability problems

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: anole: assorted stability problems
Date: 2015-05-20 19:39:04
Message-ID: 20150520193904.GL27868@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-05-20 16:21:57 -0300, Alvaro Herrera wrote:
> 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

Hm. Anole hasn't reported reliably for a while before these. It's quite
possible that this is a ac++ portability problem around the
atomics. There's lots of other IA64 animals not having problems, but
they're not using ac++.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-05-20 19:42:19 Re: RFC: Non-user-resettable SET SESSION AUTHORISATION
Previous Message Tom Lane 2015-05-20 19:37:15 Re: jsonb concatenate operator's semantics seem questionable