From: Franco Bruno Borghesi <franco@akyasociados.com.ar>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Mapping a database completly into Memory
Date: 28 Jul 2003 14:48:02 -0300
Message-ID: <1059414481.1957.1.camel@taz.oficina> (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>
But I think it's still a good option.
For example, in servers where there are other applications running (a
web server, for example) that are constantly accesing the disk and
replacing cached postgresql pages in the kernel, having shared buffers
could reduce this efect and assure the precense of our pages in
memory... I gues :)
On Mon, 2003-07-28 at 13:50, Josh Berkus wrote:
> Tom,
>
> > 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.
Attachments:
signature.asc (application/pgp-signature, 186B) download
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: franco@akyasociados.com.ar, josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Mapping a database completly into Memory
In-Reply-To: <1059414481.1957.1.camel@taz.oficina>
References: <97842368.20030727104901@artis.uni-oldenburg.de> <1059401815.749.7.camel@taz.oficina> <10185.1059409557@sss.pgh.pa.us> <200307280950.36076.josh@agliodbs.com> <1059414481.1957.1.camel@taz.oficina>
* 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