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

I don't have much choice here - these are development and
test machines, few different platforms but all on NFS.
Testing is very intensive and Postgres takes up a lot of beating.
I think this is the first time we ran into this kind of problem.

I just want to thank everyone for help.
Mike.

> -----Original Message-----
> From: Christopher Kings-Lynne [mailto:chriskl(at)familyhealth(dot)com(dot)au]
> Sent: Thursday, May 08, 2003 10:16 PM
> To: michael(at)synchronicity(dot)com; Christopher Browne
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] could not read transaction log directory ...?
>
>
> > 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
>
>