Re: "stuck spinlock"

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "stuck spinlock"
Date: 2013-12-13 17:11:38
Message-ID: D9D86CC8-4A52-4A38-9DB0-AD14C90EF5E4@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Dec 13, 2013, at 8:52 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Please apply commit 478af9b79770da43a2d89fcc5872d09a2d8731f8 and see
> if that doesn't fix it for you.

Great, thanks. Would the statement_timeout firing invoke this path? (I'm wondering why this particular installation was experiencing this.)

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-12-13 17:19:56 Re: "stuck spinlock"
Previous Message Andres Freund 2013-12-13 17:08:32 Re: pgsql: Fix a couple of bugs in MultiXactId freezing