From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | subhan alimy <salimy2011(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Transaction Rollback Error: DeadLock Detected |
Date: | 2016-02-16 18:18:28 |
Message-ID: | 56C367F4.6090006@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/15/2016 11:44 PM, subhan alimy wrote:
> Hello Everyone,
>
>
> Here I have got and error of concurrent update,
> Transaction Rollback Error: deadlock detected
> process 4801 waits for sharelock on transaction 944461 blocked by process
> 4700.
> process 4700 waits for sharelock on transaction 9444665 blocked by process
> 4801.
> by default PostgreSQL server has to abort one transaction and proceed the
> other one, in my case it did not.
What version of Postgres?
What client was doing the updates?
What was the update sequence?
What did Postgres do?
Are there any applicable error messages before or after the above?
>
>
> Solutions will highly appreciated
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/Transaction-Rollback-Error-DeadLock-Detected-tp5887760.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | jaime soler | 2016-02-16 18:35:00 | Re: ORA2PG HP-UX11i23 Itanium |
Previous Message | Chris Travers | 2016-02-16 17:24:16 | Re: Suggest note in index documentation about long running transactions |