8.2.3
Thanks
Regards
Sachchida N Ojha
sojha@secure-elements.com
Secure Elements Incorporated
198 Van Buren Street, Suite 110
Herndon Virginia 20170-5338 USA
http://www.secure-elements.com/
800-709-5011 Main
703-709-2168 Direct
703-709-2180 Fax
This email message and any attachment to this email message is intended
only for the use of the addressee(s) named above. If the reader of this
message is not the intended recipient or the employee or agent
responsible for delivering the message to the intended recipient(s),
please note that any distribution or copying of this communication is
strictly prohibited. If you have received this email in error, please
notify me immediately and delete this message. Please note that if this
email contains a forwarded message or is a reply to a prior message,
some or all of the contents of this message or any attachments may not
have been produced by the sender.
-----Original Message-----
From: Alvaro Herrera [mailto:alvherre@commandprompt.com]
Sent: Tuesday, July 31, 2007 11:28 AM
To: Sachchida Ojha
Cc: Andreas Tille; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] deadlock detected when calling function
(Callfunction_name)
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.