Re: fsync reliability

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fsync reliability
Date: 2011-04-21 16:47:02
Message-ID: BANLkTinVJeaY9UbSTkNaB84qUXSKN1gZgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 21, 2011 at 4:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> The traditional standard is that the filesystem is supposed to take
> care of its own metadata, and even Linux filesystems have pretty much
> figured that out.  I don't really see a need for us to be nursemaiding
> the filesystem.  At most there's a documentation issue here, ie,

I'm surprised by your response. If we've not documented something that
turns out to be essential to reliability of production databases, then
our users have a problem.

If our users have a data loss problem, my understanding was that we fixed it.

As it turns out, I've never personally advised anyone to use a
non-journalled filesystem, so my hands are clean in this. But it is
something we can fix, if we chose.

> we
> ought to be more explicit about which filesystems and which mount
> options we recommend.

Please be explicit then. What should the docs have said? I will update them.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2011-04-21 16:50:20 Re: Formatting Curmudgeons WAS: MMAP Buffers
Previous Message Robert Haas 2011-04-21 16:45:57 Re: fsync reliability