On Mon, 2003-11-03 at 14:24, Manfred Spraul wrote:
> Neil: what about calling posix_fadvise for the whole file immediately
> after issue_xlog_fsync() in XLogWrite? According to the comment, it's
> guaranteed that this will happen only once.
> Or: add an posix_fadvise into issue_xlog_fsync(), for the range just
> sync'ed.
I'll try those, in case it makes any difference. My guess/hope is that
it won't (as mentioned earlier), but we'll see.
> Btw, how much xlog traffic does a busy postgres site generate?
No idea. Can anyone recommend what kind of benchmark would be be
appropriate?
-Neil