| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Sachchida Ojha <sojha(at)secure-elements(dot)com> |
| Cc: | Andreas Tille <tillea(at)rki(dot)de>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: deadlock detected when calling function (Call function_name) |
| Date: | 2007-07-31 15:28:06 |
| Message-ID: | 20070731152806.GH5103@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Sachchida Ojha wrote:
>
> Hello,
> I am getting following error from my application. Can any body tell me
> how to find the process name and transaction details when the deadlock
> occurred?
>
> This problem did not occur consistently.
>
> Error log
>
> 2007-07-30 19:09:12,140 ERROR [se.em.asset.persistence.AssetUpdate]
> SQLException calling procedure{? = call update_asset_dependents(?,?,?)}
> for asset id 36
>
> org.postgresql.util.PSQLException: ERROR: deadlock detected
>
> Detail: Process 21172 waits for ShareLock on transaction 5098759;
> blocked by process 21154.
> Process 21154 waits for ShareLock on transaction 5098760; blocked by
> process 21172.
What Postgres version is this?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2007-07-31 16:16:38 | Re: disk filling up |
| Previous Message | Sachchida Ojha | 2007-07-31 15:00:48 | Re: deadlock detected when calling function (Call function_name) |