Re: Postgresql Caching

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Anon Mous <soundami(at)yahoo(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgresql Caching
Date: 2006-10-18 00:22:20
Message-ID: 1161130940.31645.213.camel@dogma.v10.wvs
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2006-10-17 at 16:51 -0700, Anon Mous wrote:
> Hi
>
> I've loved reading all of your thoughts and comments.
>
> Yet, I'm left with the question:
>
> Can we can brainstorm a caching solution that is workable...
>

I think you're making this a little complicated.

A lot of these problems can be solved with something like materialized
views (triggers updating another smaller relation), or they are already
solved by the lower layers of caching (like PostgreSQL's shared buffers,
or the OS buffer cache).

If the application is executing many queries that are exactly the same,
it would be a good idea to look at something like pgpool-II's query
cache. The only way to gain a benefit on querying results that are
already in memory is to avoid the query processing.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Douglas Toltzman 2006-10-18 00:30:01 8.1.4 verified on Intel Mac OS 10.4.8
Previous Message Anon Mous 2006-10-17 23:51:58 Re: Postgresql Caching