From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Load distributed checkpoint |
Date: | 2006-12-28 18:49:13 |
Message-ID: | 22482.1167331753@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Jim C. Nasby wrote:
>> What about the mmap/msync(?)/munmap idea someone mentioned?
> I see that as similar to using O_DIRECT during checkpoint, which had
> poor performance.
That's a complete nonstarter on portability grounds, even if msync gave
us the desired semantics, which it doesn't. It's no better than fsync
for our purposes.
To my mind the problem with fsync is not that it gives us too little
control but that it gives too much: we have to specify a particular
order of writing out files. What we'd really like is a version of
sync(2) that tells us when it's done but doesn't constrain the I/O
scheduler's choices at all. Unfortunately there's no such API ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-28 18:52:26 | Re: TODO: Add a GUC to control whether BEGIN inside |
Previous Message | Joshua D. Drake | 2006-12-28 18:46:37 | Re: TODO: GNU TLS |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-12-28 19:26:27 | Re: pg_standby |
Previous Message | Tom Lane | 2006-12-28 18:36:00 | Re: Recent SIGSEGV failures in buildfarm HEAD |