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

From Andreas Karlsson
Subject Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Date
Msg-id 648deced-f0d5-7402-b488-ca1edc496210@proxel.se
Whole thread Raw
In response to Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 04/09/2018 02:16 PM, Craig Ringer wrote:
> I'd like a middle ground where the kernel lets us register our interest 
> and tells us if it lost something, without us having to keep eight 
> million FDs open for some long period. "Tell us about anything that 
> happens under pgdata/" or an inotify-style per-directory-registration 
> option. I'd even say that's ideal.

Could there be a risk of a race condition here where fsync incorrectly 
returns success before we get the notification of that something went wrong?

Andreas


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Next
From: Andres Freund
Date:
Subject: Re: Excessive PostmasterIsAlive calls slow down WAL redo