From: Matt Clark <matt@ymogen.net>
To: Mitch Pirtle <mitch.pirtle@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Mon, 27 Sep 2004 21:19:12 +0100
Message-ID: <415875C0.3010805@ymogen.net> (raw)
In-Reply-To: <330532b604092711591491303a@mail.gmail.com>
References: <BAY18-DAV6m5UxP9Fek0002fd87@hotmail.com>
<00e801c4a4b6$5526dd30$8300a8c0@solent>
<330532b604092711591491303a@mail.gmail.com>
>Basically you set a default in seconds for the HTML results to be
>cached, and then have triggers set that force the cache to regenerate
>(whenever CRUD happens to the content, for example).
>
>Can't speak for Perl/Python/Ruby/.Net/Java, but Cache_Lite sure made a
>believer out of me!
>
>
>
Nice to have it in a library, but if you want to be that simplistic then
it's easy in any language. What if a process on server B modifies a n
important value that server A has cached though? Coherency (albeit that
the client may choose to not use it) is a must for a general solution.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: matt@ymogen.net, mitch.pirtle@gmail.com
Subject: Re: Caching of Queries
In-Reply-To: <415875C0.3010805@ymogen.net>
* 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