From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fsync reliability |
Date: | 2011-04-21 16:45:57 |
Message-ID: | BANLkTi=4FsByM0U0RWb5QLZgL97ZpoORQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-04-21 16:47:02 | Re: fsync reliability |
Previous Message | Robert Haas | 2011-04-21 16:42:30 | Re: "stored procedures" |