Re: could not read transaction log directory ...? - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: could not read transaction log directory ...?
Date
Msg-id 081a01c315d0$f91db380$6500a8c0@fhp.internal
Whole thread Raw
In response to Re: could not read transaction log directory ...?  (Michael Brusser <michael@synchronicity.com>)
Responses Re: could not read transaction log directory ...?
List pgsql-hackers
> Does this mean that you are storing your filesystems on NFS?
>
> That could well be the root of the problem; NFS has been somewhat in
> flux, and is usually not a highly recommended way of storing PG data.
>
> I hear D'Arcy Cain uses NFS fairly successfully for the purpose, but I
> believe he's using NetApp boxes, which are _quite_ different from the
> norm, and likely aren't what you are using.
>
> My first suggestion would be Stop Using NFS (unless you are really quite
> certain of what you're doing).

Or switch to FreeBSD - ever since the 'fsx' NFS automatic testing tool came
out from Apple, FreeBSD has had an excellent NFS implementation.

Chris



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: rint() replacement
Next
From: Tom Lane
Date:
Subject: Re: rint() replacement