Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

• Re: initdb and fsync at 2012-01-28 15:31:57 from Andrew Dunstan

Responses

• Re: initdb and fsync at 2012-01-28 18:46:06 from Jeff Davis
• Re: initdb and fsync at 2012-01-28 18:57:03 from Jeff Janes
• Re: initdb and fsync at 2012-02-04 21:20:05 from Florian Weimer
• Re: initdb and fsync at 2012-02-04 23:41:27 from Jeff Davis

pgsql-hackers by date

Next:	From: Jeff Janes	Date: 2012-01-28 18:27:14
	Subject: Re: initdb and fsync
Previous:	From: Jeff Davis	Date: 2012-01-28 18:16:11
	Subject: Re: initdb and fsync