From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: <rosner@scn.org>, <pgsql-interfaces@postgreSQL.org>
Subject: RE: [INTERFACES] Seeking advice on how to deal with the dreaded stuck
	spinlock problem on NT
Date: Wed, 2 Feb 2000 18:16:26 +0900
Message-ID: <001801bf6d5e$2e577460$2801007e@tpf.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3897F1B0.111D5D1D@scn.org>
Importance: Normal

> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Dan Rosner
> 
> Does anyone have any advice/suggestions about how to deal with 
> stuck spinlock problems while running postgres 6.5.3
> on cygwin B20?
> 
> Background:
> 
> Running on NT with sp6, I'm using active perl with DBI 
> and DBD-PG to load data into postgres and update some tables 
> every five minutes with a simple batch file that executes my 
> perl scripts.  Everything seems to work well for a few hours,
> but then the backend dies with the dreaded...
>        
> FATAL: s_lock(14490065) at spin.c:125, stuck spinlock. Aborting.
> 
> After this happens, I'm unable to connect to the backend unless I 
> kill and restart the ipc-daemon and postmaster again from the cygwin
> bash prompt.
> 
> I've searched the lists and have seen several references to this problem 
> on NT, but found no clear solution.  Good People, do you have any
> suggestions
> on how to deal with this? 
>

Did you apply the patch to cygipc library ?

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp