Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Date: 2013-01-09 18:39:11
Message-ID: 50EDB94F.9030503@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dimitri,

> It seems to me that pgfincore has the smarts we need to know about that,
> and that Cédric has code and refenrences for making it work on all
> platforms we care about (linux, bsd, windows for starters).

Well, fincore is Linux-only, and for that matter only more recent
versions of linux. It would be great if we could just detect the RAM,
but then we *still* have to ask the user if this is a dedicated box or not.

> Then we could have a pretty decent snapshot of the information, and
> maybe a background worker of some sort would be able to refresh the
> information while the server is running.

I don't see a background worker as necessary or even desirable; people
don't frequently add RAM to their systems. A manually callable command
would be completely adequate.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2013-01-09 18:47:46 Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Previous Message Andres Freund 2013-01-09 17:59:30 Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)