Re: Postgres, fsync, and OSs (specifically linux)
Craig Ringer <craig@2ndquadrant.com>
From: Craig Ringer <craig@2ndquadrant.com>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2018-04-30T02:14:23Z
Lists: pgsql-hackers
On 30 April 2018 at 09:09, Thomas Munro <thomas.munro@enterprisedb.com> wrote: > Considering the variety in interpretation and liberties taken, I > wonder if fsync() is underspecified and someone should file an issue > over at http://www.opengroup.org/austin/ about that. All it's going to achieve is adding an "is implementation-defined" caveat, but that's at least a bit of a heads-up. I filed patches for Linux man-pages ages ago. I'll update them and post to LKML; apparently bugzilla has a lot of spam and many people ignore notifications, so they might just bitrot forever otherwise. Meanwhile, do we know if, on Linux 4.13+, if we get a buffered write error due to dirty writeback before we close() a file we don't fsync(), we'll get the error on close()? -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
PANIC on fsync() failure.
- 9ccdd7f66e33 12.0 landed
- f1ff5f51d249 9.4.21 landed
- 312435232217 9.5.16 landed
- b9cce9ddfa17 9.6.12 landed
- afbe03f65470 10.7 landed
- 6534d544cd77 11.2 landed
-
Fix and improve pg_atomic_flag fallback implementation.
- 8c3debbbf618 11.0 cited