From: Dan Rosner <rosner@scn.org>
To: pgsql-interfaces@postgresql.org
Subject: Seeking advice on how to deal with the dreaded stuck spinlock problem on NT
Date: Wed, 02 Feb 2000 00:58:24 -0800
Message-ID: <3897F1B0.111D5D1D@scn.org> (raw)
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?
Dan
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: rosner@scn.org
Subject: Re: Seeking advice on how to deal with the dreaded stuck spinlock problem on NT
In-Reply-To: <3897F1B0.111D5D1D@scn.org>
* 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