Re: "stuck spinlock" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "stuck spinlock"
Date
Msg-id 22457.1386900929@sss.pgh.pa.us
Whole thread Raw
In response to Re: "stuck spinlock"  (Christophe Pettus <xof@thebuild.com>)
Responses Re: "stuck spinlock"
Re: "stuck spinlock"
List pgsql-hackers
Christophe Pettus <xof@thebuild.com> writes:
> On Dec 12, 2013, at 5:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Presumably, we are seeing the victim rather than the perpetrator of
>> whatever is going wrong.

> This is probing about a bit blindly, but the only thing I can see about this system that is in some way unique (and
thisis happening on multiple machines, so it's unlikely to be hardware) is that there are a relatively large number of
relations(like, 440,000+) distributed over many schemas.  Is there anything that pins a buffer that is O(N) to the
numberof relations?
 

It's not a buffer *pin* that's at issue, it's a buffer header spinlock.
And there are no loops, of any sort, that are executed while holding
such a spinlock.  At least not in the core PG code.  Are you possibly
using any nonstandard extensions?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: "stuck spinlock"
Next
From: Peter Eisentraut
Date:
Subject: Re: SSL: better default ciphersuite