| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Manfred Spraul <manfred(at)colorfullife(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)tm(dot)ee>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: adding support for posix_fadvise() |
| Date: | 2003-11-03 20:23:09 |
| Message-ID: | 1067890989.3089.540.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-11-03 20:36:57 | Re: RC1 on AIX - working thus far |
| Previous Message | Peter Eisentraut | 2003-11-03 20:21:53 | Re: 7.4RC1 tag'd, branched and bundled ... |