Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id VAA59613 for ; Wed, 7 Jul 1999 21:32:43 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id VAA18621; Wed, 7 Jul 1999 21:09:12 -0400 (EDT) From: Bruce Momjian Message-Id: <199907080109.VAA18621@candle.pha.pa.us> Subject: Re: [HACKERS] spinlock freeze again In-Reply-To: <000701bec8d3$8c5e5680$2801007e@cadzone.tpf.co.jp> from Hiroshi Inoue at "Jul 8, 1999 08:50:53 am" To: Hiroshi Inoue Date: Wed, 7 Jul 1999 21:09:12 -0400 (EDT) CC: pgsql-hackers X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > 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? -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026