Re: Enough RAM for entire Database.. cost aside, is this

From: Edmund Dengler <edmundd(at)eSentire(dot)com>
To: Mike Rylander <miker(at)purplefrog(dot)com>
Cc: Andy B <abhousehunt(at)blueyonder(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: Enough RAM for entire Database.. cost aside, is this
Date: 2004-07-08 18:12:53
Message-ID: Pine.BSO.4.58.0407081408180.1211@cyclops4.esentire.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greetings!

On Fri, 2 Jul 2004, Mike Rylander wrote:

> I find that experience does not bear this out. There is a saying a coworker
> of mine has about apps that try to solve problems, in this case caching,
> that are well understood and generally handled well at other levels of the
> "software stack"... he calls them "too smart by half" :)

But on the other hand, general algorithms which are designed to work under
a wide variety of circumstances may fail in specific cases. I am thinking
of VACUUM which would kill most caching algorithms simply because we
cannot tell the O/S "by the by, this set of pages will not be used again,
and therefore it would be fine to use almost none of the general cache to
store this". All algorithms have assumptions of value distribution and
usages. Caches depend on locality of reference, and we do not have an easy
way to say when this is broken.

Regards!
Ed

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2004-07-08 18:25:48 Re: enable thready safety on Mac OS X 10.3.4
Previous Message Stephan Szabo 2004-07-08 17:43:56 Re: Postgres doesn't use indexes for prefix matching?