Re: database errors

Michael Brusser <michael@synchronicity.com> writes:
> I wonder if message
> "open of /mnt_c1t2d0s0/... (log file 0, segment 1) failed: No such file or
> directory"
> may indicate some kind of NFS problem.

Running a database over NFS is widely considered a horrid idea --- the
NFS protocol is simply too prone to data loss.  I think you may have
a sterling example here of why not to do it :-(

The messages you quote certainly read like a badly corrupted database to
me.  In the case of a local filesystem I'd be counseling you to start
running memory and disk diagnostics.  That may still be appropriate
here, but you had better also reconsider the decision to use NFS.

If you're absolutely set on using NFS, one possibly useful tip is to
make sure it's a hard mount not a soft mount.  If your systems support
NFS-over-TCP instead of UDP, that might be worth trying too.

Also I would strongly advise an update to PG 7.3.6.  7.3.2 has serious
known bugs.
        regards, tom lane