Re: Dead Locks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Valter Nogueira <vgnogueira(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Dead Locks
Date: 2014-07-23 19:45:08
Message-ID: 25730.1406144708@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Valter Nogueira <vgnogueira(at)gmail(dot)com> writes:
> I am receiveing dead locks like this:
> Jul 22, 2014 11:00:29 PM br.com.fastway.fastdialer.FastDialerDB query
> SEVERE: SELECT * FROM ONGOING WHERE STATUS='FILA' ORDER BY TRUNK_ID,
> PRIORIDADE_TRONCO, ID;
> org.postgresql.util.PSQLException: ERROR: deadlock detected
> Detail: Process 508 waits for AccessShareLock on relation 2662 of
> database 16384; blocked by process 8504.
> Process 8504 waits for AccessExclusiveLock on relation 2663 of database
> 16384; blocked by process 508.

> What seems odd is that relations 2662 and 2663 are not user tables but
> postgres objects.

Yeah, they're indexes of pg_class. What PG version is that? Are you
perhaps running maintenance operations that try to VACUUM FULL the system
catalogs? (If so, I'd counsel against it.)

regards, tom lane

In response to

  • Dead Locks at 2014-07-23 19:38:19 from Valter Nogueira

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Krystian Bigaj 2014-07-23 19:52:39 Re:
Previous Message Valter Nogueira 2014-07-23 19:38:19 Dead Locks