| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Lee, Mija" <mija(at)scharp(dot)org> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: sig 6 on postgres server |
| Date: | 2009-03-03 02:47:16 |
| Message-ID: | 2507.1236048436@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lee, Mija | 2009-03-03 17:48:52 | Re: sig 6 on postgres server |
| Previous Message | Lee, Mija | 2009-03-03 01:02:13 | sig 6 on postgres server |