Re: finding the other statement causing a sharelock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: finding the other statement causing a sharelock
Date: 2010-11-08 20:45:12
Message-ID: 29834.1289249112@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ivan Sergio Borgonovo <mail(at)webthatworks(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-11-08 20:51:44 Re: ERROR: Out of memory - when connecting to database
Previous Message Jakub Ouhrabka 2010-11-08 20:39:45 Re: ERROR: Out of memory - when connecting to database