Skip site navigation (1) Skip section navigation (2)

Re: Caching of Queries

From: Matt Clark <matt(at)ymogen(dot)net>
To: Mitch Pirtle <mitch(dot)pirtle(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Caching of Queries
Date: 2004-09-27 20:19:12
Message-ID: 415875C0.3010805@ymogen.net (view raw or flat)
Thread:
Lists: pgsql-performance
>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.

In response to

Responses

pgsql-performance by date

Next:From: Matt ClarkDate: 2004-09-27 20:30:31
Subject: Re: Caching of Queries
Previous:From: Aaron WermanDate: 2004-09-27 20:11:53
Subject: Re: Caching of Queries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group