Re: initdb and fsync - Mailing list pgsql-hackers

From Tom Lane
Subject Re: initdb and fsync
Date
Msg-id 24164.1327774680@sss.pgh.pa.us
Whole thread Raw
In response to Re: initdb and fsync  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: initdb and fsync  (Jeff Davis <pgsql@j-davis.com>)
Re: initdb and fsync  (Jeff Janes <jeff.janes@gmail.com>)
Re: initdb and fsync  (Florian Weimer <fw@deneb.enyo.de>)
Re: initdb and fsync  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> I'm curious what problem we're actually solving here, though. I've run 
> the buildfarm countless thousands of times on different VMs, and five of 
> my seven current animals run in VMs, and I don't think I've ever seen a 
> failure ascribable to inadequately synced files from initdb.

Yeah.  Personally I would be sad if initdb got noticeably slower, and
I've never seen or heard of a failure that this would fix.

I wonder whether it wouldn't be sufficient to call sync(2) at the end,
anyway, rather than cluttering the entire initdb codebase with fsync
calls.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: initdb and fsync
Next
From: Jeff Janes
Date:
Subject: Re: initdb and fsync