For archive readers, this thread is continued as https://www.postgresql.org/message-id/20180427222842.in2e4mibx45zd...@alap3.anarazel.de and there's a follow-up lwn article at https://lwn.net/Articles/752613/ too.
- Re: PostgreSQL's handling of ... Bruce Momjian
- Re: PostgreSQL's handling of ... Craig Ringer
- Re: PostgreSQL's handling of ... Anthony Iliopoulos
- Re: PostgreSQL's handling of fsync() errors is unsafe a... Craig Ringer
- Re: PostgreSQL's handling of fsync() errors is uns... Craig Ringer
- Re: PostgreSQL's handling of fsync() errors is uns... Bruce Momjian
- Re: PostgreSQL's handling of fsync() errors is unsafe a... Andres Freund
- Re: PostgreSQL's handling of fsync() errors is uns... Bruce Momjian
- Re: PostgreSQL's handling of fsync() errors is... Thomas Munro
- Re: PostgreSQL's handling of fsync() errors is uns... Craig Ringer
- Re: PostgreSQL's handling of fsync() errors is... Craig Ringer