Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS

> On Apr 2, 2018, at 16:27, Craig Ringer <craig@2ndQuadrant.com> wrote:
>
> They're undocumented and extremely surprising semantics that are arguably a violation of the POSIX spec for fsync(),
orat least a surprising interpretation of it. 

Even accepting that (I personally go with surprising over violation, as if my vote counted), it is highly unlikely that
wewill convince every kernel team to declare "What fools we've been!" and push a change... and even if they did,
PostgreSQLcan look forward to many years of running on kernels with the broken semantics.  Given that, I think the
PANICoption is the soundest one, as unappetizing as it is. 

--
-- Christophe Pettus
   xof@thebuild.com