Re: Refactoring the checkpointer's fsync request queue - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Refactoring the checkpointer's fsync request queue
Date
Msg-id CACjxUsOfv2-AyiRESKjiwzGjwOPjjWUsrNsZmkHrqHw97-+w2A@mail.gmail.com
Whole thread Raw
In response to Re: Refactoring the checkpointer's fsync request queue  (Andres Freund <andres@anarazel.de>)
Responses Re: Refactoring the checkpointer's fsync request queue  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, Jan 22, 2019 at 2:38 PM Andres Freund <andres@anarazel.de> wrote:

> close() doesn't trigger an fsync() in general

What sort of a performance hit was observed when testing the addition
of fsync or fdatasync before any PostgreSQL close() of a writable
file, or have we not yet checked that?

> https://postgr.es/m/20180427222842.in2e4mibx45zdth5%40alap3.anarazel.de
> is, I think, a good overview, with a bunch of links.

Thanks!  Will review.

-- 
Kevin Grittner
VMware vCenter Server
https://www.vmware.com/


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: Install JIT headers
Next
From: Andres Freund
Date:
Subject: Re: Refactoring the checkpointer's fsync request queue