RE: [INTERFACES] Seeking advice on how to deal with the dreaded stuck spinlock problem on NT

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: <rosner(at)scn(dot)org>, <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: RE: [INTERFACES] Seeking advice on how to deal with the dreaded stuck spinlock problem on NT
Date: 2000-02-02 09:16:26
Message-ID: 001801bf6d5e$2e577460$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

> -----Original Message-----
> From: owner-pgsql-interfaces(at)postgreSQL(dot)org
> [mailto:owner-pgsql-interfaces(at)postgreSQL(dot)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(at)tpf(dot)co(dot)jp

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Constantin Teodorescu 2000-02-02 09:37:33 Re: [INTERFACES] PClabs Survey, Part I: Administration
Previous Message Dave Page 2000-02-02 08:58:36 RE: [INTERFACES] PClabs Survey, Part I: Administration (resend)