From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: mmap for zeroing WAL log |
Date: | 2001-02-27 22:25:03 |
Message-ID: | 13140.983312703@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org> writes:
> I had assumed that the overhead would come from synchronous
> metadata incurring writes of at least the inode, block bitmap
> and probably an indirect block for each syscall.
No Unix that I've ever heard of forces metadata to disk after each
"write" call; anyone who tried it would have abysmal performance.
That's what fsync and the syncer daemon are for.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2001-02-27 23:53:31 | Re: [ODBC] Re: Release in 2 weeks ... |
Previous Message | Matthew Kirkwood | 2001-02-27 22:20:57 | Re: mmap for zeroing WAL log |
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Kirkwood | 2001-02-28 10:32:56 | Re: mmap for zeroing WAL log |
Previous Message | Matthew Kirkwood | 2001-02-27 22:20:57 | Re: mmap for zeroing WAL log |