| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Anthony Iliopoulos <ailiop(at)altatus(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Catalin Iacob <iacobcatalin(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Date: | 2018-04-09 19:29:16 |
| Message-ID: | 20180409192916.nyrhj5rsib4pabsw@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-04-09 21:26:21 +0200, Anthony Iliopoulos wrote:
> What about having buffered IO with implied fsync() atomicity via
> O_SYNC?
You're kidding, right? We could also just add sleep(30)'s all over the
tree, and hope that that'll solve the problem. There's a reason we
don't permanently fsync everything. Namely that it'll be way too slow.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-04-09 19:29:44 | Re: Fix pg_rewind which can be run as root user |
| Previous Message | Anthony Iliopoulos | 2018-04-09 19:26:21 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |