| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] spinlock freeze again |
| Date: | 1999-07-08 01:09:12 |
| Message-ID: | 199907080109.VAA18621@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> > 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(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 | Vadim Mikheev | 1999-07-08 01:24:20 | Re: [HACKERS] Delaying insertion of default values |
| Previous Message | Bruce Momjian | 1999-07-08 00:59:04 | Re: [HACKERS] Delaying insertion of default values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 1999-07-08 02:07:10 | RE: [HACKERS] spinlock freeze again |
| Previous Message | Hiroshi Inoue | 1999-07-07 23:50:53 | RE: [HACKERS] spinlock freeze again |