From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Brown <kevin@sysexperts.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
Date: Sat, 09 Oct 2004 11:07:28 -0400
Message-ID: <27696.1097334448@sss.pgh.pa.us> (raw)
In-Reply-To: <20041009112048.GA665@filer>
References: <200410081443.16109.josh@agliodbs.com>
<m31xg8zlo4.fsf@wolfe.cbbrowne.com>
<20041009112048.GA665@filer>
Kevin Brown <kevin@sysexperts.com> writes:
> This is why I sometimes wonder whether or not it would be a win to use
> mmap() to access the data and index files --
mmap() is Right Out because it does not afford us sufficient control
over when changes to the in-memory data will propagate to disk. The
address-space-management problems you describe are also a nasty
headache, but that one is the showstopper.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, kevin@sysexperts.com
Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
In-Reply-To: <27696.1097334448@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox