From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Mapping a database completly into Memory
Date: Mon, 28 Jul 2003 12:58:19 -0400
Message-ID: <15250.1059411499@sss.pgh.pa.us> (raw)
In-Reply-To: <200307280950.36076.josh@agliodbs.com>
References: <97842368.20030727104901@artis.uni-oldenburg.de>
<1059401815.749.7.camel@taz.oficina>
<10185.1059409557@sss.pgh.pa.us>
<200307280950.36076.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
>> If we had a portable way
>> of preventing the kernel from caching the same page, it would make more
>> sense to run with large shared_buffers.
> Really? I thought we wanted to move the other way ... that is, if we could
> get over the portability issues, eliminate shared_buffers entirely and rely
> completely on the OS cache.
That seems unlikely to happen: there are cache-coherency problems if you
don't do your page-level access through shared buffers. Some have
suggested using mmap access to the data files in place of shared memory,
but that introduces a slew of issues of its own. It might happen but
I'm not holding my breath.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Mapping a database completly into Memory
In-Reply-To: <15250.1059411499@sss.pgh.pa.us>
References: <97842368.20030727104901@artis.uni-oldenburg.de> <1059401815.749.7.camel@taz.oficina> <10185.1059409557@sss.pgh.pa.us> <200307280950.36076.josh@agliodbs.com> <15250.1059411499@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