| From: | Bill Moran <wmoran(at)potentialtech(dot)com> | 
|---|---|
| To: | Martin Sarsale <martin(at)emepe3(dot)net> | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: query result set caching | 
| Date: | 2004-08-04 20:29:31 | 
| Message-ID: | 20040804162931.10670935.wmoran@potentialtech.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
Martin Sarsale <martin(at)emepe3(dot)net> wrote:
> Dear All:
> 
> Im looking for solutions (Free Software is better) to do query result
> caching.
> Thanks to the people from #postgresql I know that postgres doesn't do
> that by himself and the solution should be some kind of middle ware.
> 
> This is our problem: we are executing the same set of SELECT SP/queries
> hundreds of times, without updating the DB. We would like to cache the
> result of this SP/queries so the next time somebody runs one of them,
> the results come from the cache instead of the db.
> 
> We would like to use an already developed and tested solution but if we
> can't find anything that fits our needs, we can develop our own solution
> (playing w/ PHP and PG's LISTEN/NOTIFY)
There was a lot of talk about "materialized views" not too many months ago
on one of the PostgreSQL lists.  I believe these techniques can accomplish
what you're looking for.  An archive or google search should turn up
lots of info.
HTH.
-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Gardner | 2004-08-04 20:47:38 | Re: Updateable Views? | 
| Previous Message | Martin Sarsale | 2004-08-04 20:06:11 | query result set caching |