Re: sig 6 on postgres server

Thanks for the response, Tom. We do have hard mounts, and unfortunately,
we are dependent on nfs.

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, March 02, 2009 6:47 PM
To: Lee, Mija
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] sig 6 on postgres server

"Lee, Mija" <mija(at)scharp(dot)org> writes:
> Recently I had a postgres instance shut down & restart, and I'm trying
> to understand why. I'm running 8.3.5 on solaris 10, with the data
> directory on a netapp. The postgres log shows an error associated with
> some of the critical application tables not existing, then it was
unable
> to write to the log, then a sigabrt.

> cpas 2009-03-02 14:58:34 PSTPANIC: could not write to log file 93,
> segment 240 at offset 9560064, length 8192: Interrupted system call

EINTR? Hmm, I wonder if you have the data directory on a "soft" NFS
mount? We tend not to trust NFS too much at all around here, but if
you have to use it, hard-mount is more reliable than soft.

regards, tom lane