> Bruce Momjian <[EMAIL PROTECTED]> writes: > > Is there significant time between entry of CommitTransaction() and the > > fsync()? Maybe not. > > I doubt it. No I/O anymore, anyway, unless the commit record happens to > overrun an xlog block boundary. That's what I was afraid of. Since we don't write the dirty blocks to the kernel anymore, we don't really have much happening before someone says they are about to commit. In the old days, we were write()'ing those buffers, and we had some delay and kernel calls in there. Guess that idea is dead. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
- [HACKERS] CommitDelay performance improvement Tom Lane
- Re: [HACKERS] CommitDelay performance improvement Bruce Momjian
- Re: [HACKERS] CommitDelay performance improvement Tom Lane
- Re: [HACKERS] CommitDelay performance improveme... Bruce Momjian
- Re: [HACKERS] CommitDelay performance impro... Tom Lane
- Re: [HACKERS] CommitDelay performance ... Bruce Momjian
- Re: [HACKERS] CommitDelay performance improvement Nathan Myers
- Re: [HACKERS] CommitDelay performance improvement Bruce Momjian
- Re: [HACKERS] CommitDelay performance improvement Tom Lane
- Re: [HACKERS] CommitDelay performance improveme... Bruce Momjian
- Re: [HACKERS] CommitDelay performance impro... Tom Lane
- Re: [HACKERS] CommitDelay performance ... Bruce Momjian
- Re: [HACKERS] CommitDelay performa... Tom Lane
- Re: [HACKERS] CommitDelay perf... Bruce Momjian
- Re: [HACKERS] CommitDelay perf... Tom Lane
- Re: [HACKERS] CommitDelay perf... Bruce Momjian