| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postgres, fsync, and OSs (specifically linux) |
| Date: | 2018-04-30 02:14:23 |
| Message-ID: | CAMsr+YG6Eo=z7EXK=V+5-iimyWOAixOpd39dOxmzw6am=Rh66Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30 April 2018 at 09:09, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-04-30 02:17:38 | Re: Postgres, fsync, and OSs (specifically linux) |
| Previous Message | Yuriy Zhuravlev | 2018-04-30 02:01:14 | Re: Is a modern build system acceptable for older platforms |