From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kevin Brown <kevin(at)sysexperts(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: First set of OSDL Shared Mem scalability results, some wierdness ... |
Date: | 2004-10-15 05:13:36 |
Message-ID: | 5235.1097817216@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> Hmm...something just occurred to me about this.
> Would a hybrid approach be possible? That is, use mmap() to handle
> reads, and use write() to handle writes?
Nope. Have you read the specs regarding mmap-vs-stdio synchronization?
Basically it says that there are no guarantees whatsoever if you try
this. The SUS text is a bit weaselly ("the application must ensure
correct synchronization") but the HPUX mmap man page, among others,
lays it on the line:
It is also unspecified whether write references to a memory region
mapped with MAP_SHARED are visible to processes reading the file and
whether writes to a file are visible to processes that have mapped the
modified portion of that file, except for the effect of msync().
It might work on particular OSes but I think depending on such behavior
would be folly...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Katsaros Kwn/nos | 2004-10-15 07:15:25 | Re: Networking feature for postgresql... |
Previous Message | Bruce Momjian | 2004-10-15 04:24:34 | Re: Strange code in initdb |
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Medici (NetCentrex) | 2004-10-15 07:28:18 | Re: View & Query Performance |
Previous Message | Iain | 2004-10-15 01:41:35 | Re: Performance vs Schemas |