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

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: <michael(at)synchronicity(dot)com>, "Christopher Browne" <cbbrowne(at)cbbrowne(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: could not read transaction log directory ...?
Date: 2003-05-09 02:16:15
Message-ID: 081a01c315d0$f91db380$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-05-09 02:34:28 Re: rint() replacement
Previous Message Bruce Momjian 2003-05-09 02:12:16 rint() replacement