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

From Greg Stark
Subject Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Date
Msg-id CAM-w4HMdr-GnUYSZisEYqwSdf38HoifTRsCgoPyyeigzD0pDKQ@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On 10 April 2018 at 19:58, Joshua D. Drake <jd@commandprompt.com> wrote:
> You can't unmount the file system --- that requires writing out all of the pages
> such that the dirty bit is turned off.

I always wondered why Linux didn't implement umount -f. It's been in
BSD since forever and it's a major annoyance that it's missing in
Linux. Even without leaking memory it still leaks other resources,
causes confusion and awkward workarounds in UI and automation
software.

-- 
greg


pgsql-hackers by date:

Previous
From: Jonathan Corbet
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Next
From: Đặng Minh Hướng
Date:
Subject: Re: User defined data types in Logical Replication