RE: [HACKERS] spinlock freeze again
От | Hiroshi Inoue |
---|---|
Тема | RE: [HACKERS] spinlock freeze again |
Дата | |
Msg-id | 000901bec8e6$967c14a0$2801007e@cadzone.tpf.co.jp обсуждение исходный текст |
Ответ на | Re: [HACKERS] spinlock freeze again (Bruce Momjian <maillist@candle.pha.pa.us>) |
Ответы |
Re: [HACKERS] spinlock freeze again
|
Список | pgsql-hackers |
> -----Original Message----- > From: Bruce Momjian [mailto:maillist@candle.pha.pa.us] > Sent: Thursday, July 08, 1999 10:09 AM > To: Hiroshi Inoue > Cc: pgsql-hackers > Subject: Re: [HACKERS] spinlock freeze again > > > > > Are their any locks acquired before InitProcess()? > > > > > > > OidGenLockId spinlock is acquired in InitTransactionLog(). > > > > Regards. > > > > Well, seems we have a Proc queue that holds locks, but for these other > cases, we don't. We could use the on_shmexit queue to add an cleanup > handler once we get the lock, and remove it from the queue once we > release the lock. We don't currently have the ability to remove > specific queue entries, but we could easily do that. > > Is the lock failure a problem that happens a lot? > It doesn't happen oridinarily. I don't remember well how it happend. Probably it was caused by other spinlock(io_in_progress_lock ?) freeze while testing 6.5-beta. Regards. Hiroshi Inoue Inoue@tpf.co.jp
В списке pgsql-hackers по дате отправления: