From: Bruce Momjian <maillist@candle.pha.pa.us>
To: Hiroshi Inoue <Inoue@tpf.co.jp>
Cc: pgsql-hackers <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] spinlock freeze again
Date: Wed, 7 Jul 1999 21:09:12 -0400 (EDT)
Message-ID: <199907080109.VAA18621@candle.pha.pa.us> (raw)
In-Reply-To: <000701bec8d3$8c5e5680$2801007e@cadzone.tpf.co.jp>
> > 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: maillist@candle.pha.pa.us, Inoue@tpf.co.jp, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] spinlock freeze again
In-Reply-To: <199907080109.VAA18621@candle.pha.pa.us>
References: <000701bec8d3$8c5e5680$2801007e@cadzone.tpf.co.jp> <199907080109.VAA18621@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox