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

> On Apr 7, 2018, at 19:33, Bruce Momjian <bruce@momjian.us> wrote:
> Idea 4 would be for people to assume their database is corrupt if their
> server logs report any I/O error on the file systems Postgres uses.

Pragmatically, that's where we are right now.  The best answer in this bad situation is (a) fix the error, then (b)
replayfrom a checkpoint before the error occurred, but it appears we can't even guarantee that a PostgreSQL process
willbe the one to see the error. 

--
-- Christophe Pettus
   xof@thebuild.com