| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | PostgreSQL-development <hackers(at)postgreSQL(dot)org>, "Vadim B(dot) Mikheev" <vadim(at)krs(dot)ru> |
| Subject: | Re: [HACKERS] can't compile |
| Date: | 1999-05-06 05:25:28 |
| Message-ID: | 199905060525.BAA15170@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Does your chanage in LockResolveConflicts() work fine ?
>
> if (SHMQueueEmpty(&MyProc->lockQueue) && waitQueue->size &&
> topproc->prio > myprio)
> {
>
> First, LockResolveConflicts() is called not only from LockAcquire() but also
> from ProcLockWakeup(). ProcLockWakeup() is called from a lock releasing
> process. Does it make sense to check MyProc->lockQueue ?
>
> Second,when LockAcquire() calls LockResolveConflicts(),MyProc->lockQueue
> is always not empty. So does it make sense too ?
Seems it does not work, as Vadim has pointed out. Seems he wants to
work on fixing this.
I am curious what lock is in the lockQueue when it is called from
LockAcquire()?
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 1999-05-06 05:59:14 | Re: [HACKERS] posmaster failed under high load |
| Previous Message | Bruce Momjian | 1999-05-06 05:20:13 | Re: [HACKERS] posmaster failed under high load |