Alfred Perlstein <[EMAIL PROTECTED]> writes: > It might make more sense to keep a private copy of the last time > the file was modified per-backend by that particular backend and > a timestamp of the last fsync shared globally so one can forgo the > fsync if "it hasn't been dirtied by me since the last fsync" > This would provide a rendevous point for the fsync call although > cost more as one would need to periodically call gettimeofday to > set the modified by me timestamp as well as the post-fsync shared > timestamp. That's the hard way to do it. We just need to keep track of the endpoint of the log as of the last fsync. You need to fsync (after returning from sleep()) iff your commit record position > fsync endpoint. No need to ask the kernel for time-of-day. regards, tom lane
- Re: [HACKERS] WAL fsync schedul... Peter Eisentraut
- Re: [HACKERS] WAL fsync schedul... Vadim Mikheev
- Re: [HACKERS] WAL fsync schedul... Bruce Momjian
- Re: [HACKERS] WAL fsync schedul... Bruce Momjian
- Re: [HACKERS] RE: [COMMITTERS] ... Bruce Momjian
- Re: [HACKERS] RE: [COMMITTERS] ... Peter Eisentraut
- Re: [HACKERS] RE: [COMMITTERS] ... Bruce Momjian
- Re: [HACKERS] RE: [COMMITTERS] ... Alfred Perlstein
- Re: [HACKERS] RE: [COMMITTERS] ... Bruce Momjian
- Re: [HACKERS] RE: [COMMITTERS] ... Alfred Perlstein
- Re: [HACKERS] RE: [COMMITTERS] ... Tom Lane
- Re: [HACKERS] RE: [COMMITTERS] ... Alfred Perlstein
- Re: [HACKERS] RE: [COMMITTERS] ... Tom Lane
- RE: [HACKERS] RE: [COMMITTERS] pgsql/src/backend/access/t... Mikheev, Vadim
- RE: [HACKERS] RE: [COMMITTERS] pgsql/src/backend/access/t... Mikheev, Vadim