Re: finding the other statement causing a sharelock

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