Re: finding the other statement causing a sharelock - Mailing list pgsql-general

From Tom Lane
Subject Re: finding the other statement causing a sharelock
Date
Msg-id 29834.1289249112@sss.pgh.pa.us
Whole thread Raw
In response to finding the other statement causing a sharelock  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
Responses Re: finding the other statement causing a sharelock
List pgsql-general
Ivan Sergio Borgonovo <mail@webthatworks.it> writes:
> I get
> DETAIL:  Process 24749 waits for ShareLock on transaction 113443492;
> blocked by process 25199. Process 25199 waits for ShareLock on
> transaction 113442820; blocked by process 24749.

> I would like to know both statements that caused the sharelock
> problem.

Recent versions of PG record both (or all) statements involved in a
deadlock in the postmaster log.

            regards, tom lane

pgsql-general by date:

Previous
From: Michael Glaesemann
Date:
Subject: Removing pgsql_tmp files
Next
From: Tom Lane
Date:
Subject: Re: ERROR: Out of memory - when connecting to database