Re: Re[2]: Allowing WAL fsync to be done via O_SYNC
От | Bruce Momjian |
---|---|
Тема | Re: Re[2]: Allowing WAL fsync to be done via O_SYNC |
Дата | |
Msg-id | 200103161511.KAA08993@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Re[2]: Allowing WAL fsync to be done via O_SYNC (Alfred Perlstein <bright@wintelcom.net>) |
Ответы |
Re: Re[2]: Allowing WAL fsync to be done via O_SYNC
|
Список | pgsql-hackers |
> > 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. > > I suggested this about a year ago. :) > > The problem is that you need that process to potentially open and close > many files over and over. > > I still think it's somewhat of a good idea. I like the idea too, but people want the transaction to return COMMIT only after data has been fsync'ed so I don't see a big win. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: