From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | Michał Nowak <minowack(at)wp(dot)pl> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: semop hanging - Postgres 9.4.4 |
Date: | 2015-12-16 13:41:37 |
Message-ID: | CACjxUsM2MCZsWR7kixr=Ck6rFPsKw9RRjh_J6Cjua6NUp18P2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Dec 15, 2015 at 1:34 PM, Michał Nowak <minowack(at)wp(dot)pl> wrote:
> postgres=# select version();
> version
> ------------------------------------------------------------------------------------------------------
> PostgreSQL 9.4.4 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2, 64-bit
There is a bug fix in 9.4.5 which can cause a deadlock on
lightweight locking.
http://www.postgresql.org/support/versioning/
From a subsequent post:
> perf top:
>
> 17.04% postgres [.] _bt_moveright
> 13.39% postgres [.] LWLockAcquire
> 8.82% postgres [.] LWLockRelease
> 8.11% postgres [.] _bt_checkpage
The perf top output suggests the possibility of a corrupted index,
causing an endless loop.
Can you get a few stack traces from "stuck" backends?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | CN | 2015-12-17 07:44:05 | feature request: pg_restore renaming target schema |
Previous Message | Alvaro Herrera | 2015-12-16 13:22:00 | Re: [REASSIGN confusion] |