On 10/28/2016 10:25 AM, Tom Lane wrote:
Steve Clark writes:
On 10/28/2016 09:48 AM, Tom Lane wrote:
Retrying might be a usable band-aid, but really this is an application
logic error. The code that is trying to do "lock table t_unit in
exclusive mode" must already hold some lower-level lock o
Steve Clark writes:
> On 10/28/2016 09:48 AM, Tom Lane wrote:
>> Retrying might be a usable band-aid, but really this is an application
>> logic error. The code that is trying to do "lock table t_unit in
>> exclusive mode" must already hold some lower-level lock on t_unit, which
>> is blocking wh
On 10/28/2016 09:48 AM, Tom Lane wrote:
Steve Clark writes:
No. But I examined the pg_log/log_file and saw an error indicating it was
autovacuum:
2016-10-27 09:47:02 EDT:srm2api:12968:LOG: sending cancel to blocking
autovacuum PID 12874
2016-10-27 09:47:02 EDT:srm2api:12968:DETAIL: Process
Steve Clark writes:
> No. But I examined the pg_log/log_file and saw an error indicating it was
> autovacuum:
> 2016-10-27 09:47:02 EDT:srm2api:12968:LOG: sending cancel to blocking
> autovacuum PID 12874
> 2016-10-27 09:47:02 EDT:srm2api:12968:DETAIL: Process 12968 waits for
> ExclusiveLock
On 10/28/16 9:27 AM, Steve Clark wrote:
> On 10/28/2016 09:15 AM, Adrian Klaver wrote:
>> On 10/28/2016 05:28 AM, Steve Clark wrote:
>>> Hello List,
>>>
>>> I am occasionally seeing the following error:
>>> ALERT 3 sqlcode=-400 errmsg=deadlock detected on line 3351
>> So what exactly is it doing
Steve Clark writes:
> I am occasionally seeing the following error:
> ALERT 3 sqlcode=-400 errmsg=deadlock detected on line 3351
This isn't nearly enough information to determine what is going on.
But if that is a report of a server-detected deadlock error, there
should be more information about
On 10/28/2016 09:15 AM, Adrian Klaver wrote:
On 10/28/2016 05:28 AM, Steve Clark wrote:
Hello List,
I am occasionally seeing the following error:
ALERT 3 sqlcode=-400 errmsg=deadlock detected on line 3351
So what exactly is it doing at line 3351?
from an application written using ecpg when
On 10/28/2016 05:28 AM, Steve Clark wrote:
Hello List,
I am occasionally seeing the following error:
ALERT 3 sqlcode=-400 errmsg=deadlock detected on line 3351
So what exactly is it doing at line 3351?
from an application written using ecpg when trying an update to the table.
Can autovacuum
Hello List,
I am occasionally seeing the following error:
ALERT 3 sqlcode=-400 errmsg=deadlock detected on line 3351
from an application written using ecpg when trying an update to the table.
Can autovacuum be causing this,
since no one else is updating this database table.
Thanks,
--
Stephen
