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

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
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-24 13:40:32
Message-ID: 199905241340.JAA20372@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Tatsuo Ishii wrote:
> >
> > > > I get above message from the backend while trying to update same raw
> > > > from different transactions (I guess). Is this normal?
> >
> > My sessions look like:
> >
> > begin;
> > update t set a = 1 where c = 1;
> > select * from t where c = 1;
> > end;
>
> Ops. Do you have indices over table t?
> 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?

If you don't, seems like our MVCC isn't going to be much good.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-24 13:45:27 Re: [GENERAL] Full Text Searches
Previous Message Keith Parks 1999-05-24 13:21:07 Re: [HACKERS] 6.5 cvs: views doesn't survives after pg_dump (fwd)