Re: could not read transaction log directory ...?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: michael(at)synchronicity(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: could not read transaction log directory ...?
Date: 2003-05-08 13:55:06
Message-ID: 19839.1052402106@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Brusser <michael(at)synchronicity(dot)com> writes:
> "Cookie is stale" - ..?
> Should I consider some problems with the file server?

Running a database over an NFS mount is widely considered foolish.
It exposes you to all sorts of failure modes that don't exist with
a local filesystem.

> The strange thing is that process always crashes some 30 minutes
> after start.

Well, that would fit fine with the notion that there's some kind of
30-minute timeout on open files in your NFS stack.

> Another point is that it works fine on another machine -
> Red Hat 7.2 with 2.4.9 kernel.
> I'm not sure what to make out of this.

I'd call it a kernel bug or NFS server bug.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-05-08 14:10:02 Re: Protocol V3 questions (StartupMessage and ParameterStatus)
Previous Message Ben Clewett 2003-05-08 13:52:02 Pocket PC, AKA, MS CE