Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
From:
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To:
Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc:
Bruce Momjian <bruce(at)momjian(dot)us>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Anthony Iliopoulos <ailiop(at)altatus(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, 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
Note: as I've brought up in another thread, it turns out that PG is not handling fsync errors correctly even when the OS _does_ do the right thing (discovered by testing on FreeBSD).