Re: initdb and fsync - Mailing list pgsql-hackers

From Tom Lane
Subject Re: initdb and fsync
Date
Msg-id 26056.1342215306@sss.pgh.pa.us
Whole thread Raw
In response to Re: initdb and fsync  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: initdb and fsync  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
I wrote:
> I'm picking up this patch now.  What I'm inclined to do about the -N
> business is to commit without that, so that we get a round of testing
> in the buildfarm and find out about any portability issues, but then
> change to use -N after a week or so.  I agree that in the long run
> we don't want regression tests to run with fsyncs by default.

Committed without the -N in pg_regress (for now).  I also stuck
sync_file_range into the backend's pg_flush_data --- it would be
interesting to hear measurements of whether that makes a noticeable
difference for CREATE DATABASE.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Re: [PATCH] lock_timeout and common SIGALRM framework
Next
From: Boszormenyi Zoltan
Date:
Subject: Re: [PATCH] lock_timeout and common SIGALRM framework