Re: "stuck spinlock"

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "stuck spinlock"
Date: 2013-12-13 04:20:12
Message-ID: 14CE3DF6-4224-4D19-890D-593C4C2EC0DE@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Dec 12, 2013, at 7:40 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> Couldn't that just be the app setting it locally?

Yes, that's what is happening there (I had to check with the client's developers). It's possible that the one-minute repeat is due to the application reissuing the query, rather than specifically related to the spinlock issue. What this does reveal is that all the spinlock issues have been on long-running queries, for what it is worth.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip kumar 2013-12-13 04:51:37 Re: Logging WAL when updating hintbit
Previous Message Michael Paquier 2013-12-13 03:48:03 Re: [PATCH] configure: allow adding a custom string to PG_VERSION