Re[2]: Allowing WAL fsync to be done via O_SYNC - Mailing list pgsql-hackers

From Xu Yifeng
Subject Re[2]: Allowing WAL fsync to be done via O_SYNC
Date
Msg-id 7420422776.20010316142600@telekbird.com.cn
Whole thread Raw
In response to Re: Allowing WAL fsync to be done via O_SYNC  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re[2]: Allowing WAL fsync to be done via O_SYNC  (Alfred Perlstein <bright@wintelcom.net>)
List pgsql-hackers
Hello Tom,

Friday, March 16, 2001, 6:54:22 AM, you wrote:

TL> Alfred Perlstein <bright@wintelcom.net> writes:
>> How many files need to be fsync'd?

TL> Only one.

>> If it's more than one, what might work is using mmap() to map the
>> files in adjacent areas, then calling msync() on the entire range,
>> this would allow you to batch fsync the data.

TL> Interesting thought, but mmap to a prespecified address is most
TL> definitely not portable, whether or not you want to assume that
TL> plain mmap is ...

TL>                         regards, tom lane

Could anyone consider fork a syncer process to sync data to disk ?
build a shared sync queue, when a daemon process want to do sync after
write() is called, just put a sync request to the queue. this can release
process from blocked on writing as soon as possible. multipile sync
request for one file can be merged when the request is been inserting to
the queue.

-- 
Regards,
Xu Yifeng




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Allowing WAL fsync to be done via O_SYNC
Next
From: Alfred Perlstein
Date:
Subject: Re: Re[2]: Allowing WAL fsync to be done via O_SYNC