Re: How to prevent vacuum and reindex from deadlocking.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Creager <Robert_Creager(at)LogicalChaos(dot)org>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to prevent vacuum and reindex from deadlocking.
Date: 2003-08-11 14:11:37
Message-ID: 2084.1060611097@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> writes:
> Opps, if it helps, the log of the deadlock:

> Aug 10 14:19:36 thunder postgres[18735]: [2-1] ERROR: deadlock detected

> Aug 10 14:19:36 thunder postgres[18735]: [2-2] DETAIL: Proc 18735 waits
> for AccessExclusiveLock on relation 18028 of database 17140; blocked by
> proc 18815.

> Aug 10 14:19:36 thunder postgres[18735]: [2-3] Proc 18815 waits for
> AccessExclusiveLock on relation 18101 of database 17140; blocked by proc
> 18735.

What tables do the two referenced OIDs correspond to? Also, which
process was doing what, exactly?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-08-11 14:21:43 Re: 7.4Beta1 "failed to create socket: Address family not supported by protocol"
Previous Message Martijn van Oosterhout 2003-08-11 12:56:50 Re: Join faster than single table query