Re: How to prevent vacuum and reindex from deadlocking. - Mailing list pgsql-general

From Tom Lane
Subject Re: How to prevent vacuum and reindex from deadlocking.
Date
Msg-id 2084.1060611097@sss.pgh.pa.us
Whole thread Raw
In response to Re: How to prevent vacuum and reindex from deadlocking.  (Robert Creager <Robert_Creager@LogicalChaos.org>)
Responses Re: How to prevent vacuum and reindex from deadlocking.  (Robert Creager <Robert_Creager@LogicalChaos.org>)
List pgsql-general
Robert Creager <Robert_Creager@LogicalChaos.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

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Join faster than single table query
Next
From: Tom Lane
Date:
Subject: Re: 7.4Beta1 "failed to create socket: Address family not supported by protocol"