Re: REINDEX deadlock - Postgresql -9.1

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: REINDEX deadlock - Postgresql -9.1
Date: 2013-02-11 05:01:48
Message-ID: 51187B3C.9030403@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/6/2013 1:28 AM, Anoop K wrote:
> 3 connections are going in to some dead lock state.
>
> 1. *idle in transaction *
> 2. *REINDEX waiting *
> 3. *SELECT waiting *
>

you need to track down what resources are being locked by those
processes, by joining pg_stat_activity against pg_locks and.... (been
awhile, I forget the magic join query that gives you useful info here)

IDLE in Transaction means that connection did a BEGIN; but isn't
executing any commands at all at present and is just sitting there. This
should never happen, and is generally a sign of buggy application
software, or poorly designed ORM or something.

--
john r pierce 37N 122W
somewhere on the middle of the left coast

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sergey Konoplev 2013-02-11 05:46:33 Re: REINDEX deadlock - Postgresql -9.1
Previous Message james.sewell 2013-02-11 02:51:49 archive_mode=on on a Slave in streaming replication mode