RE: [HACKERS] Frustration

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Monday, September 27, 1999 10:20 PM
> To: Hiroshi Inoue
> Cc: Michael Simms; pgsql-hackers@postgreSQL.org
> Subject: Re: [HACKERS] Frustration 
> 
> 
> "Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> > Different from other spinlocks,io_in_progress spinlock is a per bufpage
> > spinlock and ProcReleaseSpins() doesn't release the spinlock.
> > If an error(in md.c in most cases) occured while holding the spinlock
> > ,the spinlock would necessarily freeze.
> 
> Oooh, good point.  Shouldn't this be fixed?  If we don't fix it, then

Yes,it's on TODO.
* spinlock stuck problem when elog(FATAL) and elog(ERROR) inside bufmgr

I would try to fix it.
> a disk I/O error will translate to an installation-wide shutdown and
> restart as soon as some backend tries to touch the locked page (as
> indeed was happening to Michael).  That seems a tad extreme.
> 

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp