| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Shawn Debnath <sdn(at)amazon(dot)com> |
| Subject: | Re: Refactoring the checkpointer's fsync request queue |
| Date: | 2019-01-22 20:53:11 |
| Message-ID: | CACjxUsOfv2-AyiRESKjiwzGjwOPjjWUsrNsZmkHrqHw97-+w2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 22, 2019 at 2:38 PM Andres Freund <andres(at)anarazel(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-01-22 21:01:52 | Re: Refactoring the checkpointer's fsync request queue |
| Previous Message | David Fetter | 2019-01-22 20:51:57 | Re: Install JIT headers |