Re: fsync reliability

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fsync reliability
Date: 2011-04-21 16:53:02
Message-ID: BANLkTin+17r8Dvw+4zNuoXcpZ8+tj6NUBg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 21, 2011 at 5:45 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Apr 21, 2011 at 11:55 AM, 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, we
>> ought to be more explicit about which filesystems and which mount
>> options we recommend.
>
> I think it would be illuminating to shine upon this conversation the
> light of some actual facts, as to whether or not this can be
> demonstrated to be broken on systems people actually use, and to what
> extent it can be mitigated by the sorts of configuration choices you
> mention.  Neither Simon's comments nor yours give me any clear feeling
> as to how likely this is to cause problems for real users, nor how
> easily those problems can be mitigated.

If you have some actual facts yourself, add them. Or listen for people that do.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-04-21 16:59:15 EOL for 8.2 (was Re: Formatting Curmudgeons WAS: MMAP Buffers)
Previous Message Christopher Browne 2011-04-21 16:50:20 Re: Formatting Curmudgeons WAS: MMAP Buffers