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

Claudio,

> Not really. I'm convinced, and not only for e_c_s, that
> autoconfiguration is within the realm of possibility.

Hey, if you can do it, my hat's off to you.

> In any case, as eavesdroppers can infer a cryptographic key by timing
> operations or measuring power consumption, I'm pretty sure postgres
> can infer cost metrics and/or time sharing with clever
> instrumentation. The trick lies in making such instrumentation
> uninstrusive.

... and not requiring a great deal of code maintenance for each and
every release of Linux and Windows.

Anyway, we could do something for 9.3 if we just make "available RAM" a
manual setting.  Asking the user "how much RAM is available for
Postgres" is not a terribly difficult question.

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