Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint
От | Bruce Momjian |
---|---|
Тема | Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint |
Дата | |
Msg-id | 200401301721.i0UHLsi12233@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint
|
Список | pgsql-hackers |
Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > The trick is to somehow record all files modified since the last > > checkpoint, and open/fsync/close each one. My idea is to stat() each > > file in each directory and compare the modify time to determine if the > > file has been modified since the last checkpoint. > > This seems a complete non-starter, as stat() generally has at best > one-second resolution on mod times, even if you assume that the kernel > keeps mod time fully up-to-date at all times. In any case, it's > difficult to believe that stat'ing everything in a database directory > will be faster than keeping track of it for ourselves. Yes, we would have to have a slop factor and fsync anything more than one second before the last checkpoint. Any ideas on how to record the modified files without generating tones of output or locking contention? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
В списке pgsql-hackers по дате отправления: