| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "stuck spinlock" |
| Date: | 2013-12-13 22:57:09 |
| Message-ID: | 8EA4CE45-35F8-4000-9C48-55C3958C2517@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 13, 2013, at 1:49 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> Is this an edge case or something that will hit a lot of users?
My understanding (Tom can correct me if I'm wrong, I'm sure) is that it is an issue for servers on 9.3.2 where there are a lot of query cancellations due to facilities like statement_timeout or lock_timeout that cancel a query asynchronously. I assume pg_cancel_backend() would apply as well.
We've only seen it on one client, and that client had a *lot* (thousands on thousands) of statement_timeout cancellations.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2013-12-13 22:58:56 | Re: "stuck spinlock" |
| Previous Message | Merlin Moncure | 2013-12-13 21:49:45 | Re: "stuck spinlock" |