Re: [HACKERS] ERROR: WaitOnLock: error on wakeup - Aborting this transaction

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: Vadim Mikheev <vadim(at)krs(dot)ru>
Cc: t-ishii(at)sra(dot)co(dot)jp, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] ERROR: WaitOnLock: error on wakeup - Aborting this transaction
Date: 1999-05-26 06:07:33
Message-ID: 199905260607.PAA00202@srapc451.sra.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> >Btree-s are still using page-level locking and don't release
>> >locks when leave index page to fetch row from relation.
>> >Seems that this causes deadlocks more often than I thought -:(
>> >
>> >Marc? I can fix this today and I'll be very careful...
>> >Ok?
>>
>> Please let me know if you fix it. I will run the test again.
>
>Fixed.

Thanks, but I now have another problem. I got backend abortings. Stack
trace shows followings (Sorry I' writing this by hand rather than
cut&paste, so there may be an error):

s_lock_stuck
s_lock
SpinAcquire
LockAcquire
LockRelation
heap_beginscan
index_info
find_secondary_index
find_relation_indices
set_base_rel_pathlist
make_one_rel
subPlanner
query_planner
union_planner
planner
pg_parse_and_plan
pg_exec_query_dest
pg_exec_quer
:
:

Note that this happend in both read committed/serializable levels.
--
Tatsuo Ishii

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ari Halberstadt 1999-05-26 06:10:47 Re: [HACKERS] pg_dump core dump, upgrading from 6.5b1 to 5/24 snapshot
Previous Message Don Baccus 1999-05-26 05:13:21 Re: [HACKERS] pg_dump inconsistences