Re: Unexpected data beyond EOF during heavy writes

From: Rosser Schwarz <rosser(dot)schwarz(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tony Sullivan <tsullivan(at)blackducksoftware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unexpected data beyond EOF during heavy writes
Date: 2010-05-20 21:38:41
Message-ID: AANLkTimuSgUqyN898MptX4B-7cFWcvVBfCjUQQYd5r_M@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 20, 2010 at 3:19 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:

> We (at Command Prompt) researched this recently for another setup and
> the common point you both have is NetApp.  I then wondered about a bug
> in NetApp driver or NFS client implementation.

It's definitely not (just) NetApp, though it may be their NFS -- or
NFS in general; I couldn't say. I can't speak to their NFS
implementation, beyond having generally heard good things about it,
but I've run PostgreSQL on filers for years, and have never seen that
message. Granted, I've only been iSCSI- or fibre-attached (or had the
storage path abstracted away by some form of virtualization), so I
haven't seen every possible use-case.

In general, though, I'd be pretty wary of running postgres on an NFS
mount. I know a lot of people run Oracle that way, but at the
filesystem level, there are some vast differences between the two.

Has anyone ever seen this message on non-NetApp NFS?

rls

--
:wq

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-05-20 22:11:44 Re: Postgres stats collector showing high disk I/O
Previous Message Alvaro Herrera 2010-05-20 21:24:59 Re: Postgres stats collector showing high disk I/O