Re: Quite strange crash - Mailing list pgsql-hackers

From Denis Perchine
Subject Re: Quite strange crash
Date
Msg-id 0101091155090A.00613@dyp.perchine.com
Whole thread Raw
In response to Re: Quite strange crash  (ncm@zembu.com (Nathan Myers))
Responses Re: Quite strange crash
List pgsql-hackers
> > Well, I found a smoking gun: ...
> > What seems to have happened is that 2501 curled up and died, leaving
> > one or more buffer spinlocks locked.  ...
> > There is something pretty fishy about this.  You aren't by any chance
> > running the postmaster under a ulimit setting that might cut off
> > individual backends after a certain amount of CPU time, are you?
> > What signal does a ulimit violation deliver on your machine, anyway?
>
> It's worth noting here that modern Unixes run around killing user-level
> processes more or less at random when free swap space (and sometimes
> just RAM) runs low.  AIX was the first such, but would send SIGDANGER
> to processes first to try to reclaim some RAM; critical daemons were
> expected to explicitly ignore SIGDANGER. Other Unixes picked up the
> idea without picking up the SIGDANGER behavior.

That's not the case for sure. There are 512Mb on the machine, and when I had 
this problem it was compltely unloaded (>300Mb in caches).

-- 
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: V7.0 Error: OID ##### no longer exists in pg_databas e
Next
From: Tom Lane
Date:
Subject: Re: Quite strange crash