| From: | Jeff <threshar(at)torgo(dot)978(dot)org> |
|---|---|
| To: | Mitch Pirtle <mitch(dot)pirtle(at)gmail(dot)com> |
| Cc: | Aaron Werman <awerman(at)hotmail(dot)com>, Scott Kirkwood <scottakirkwood(at)gmail(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-performance(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Caching of Queries |
| Date: | 2004-09-27 18:25:55 |
| Message-ID: | ABA05F02-10B2-11D9-99D5-000D9366F0C4@torgo.978.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
[ discussion of server side result caching ]
and lets not forget PG's major fork it will throw into things: MVCC
The results of query A may hold true for txn 1, but not txn 2 and so on
.
That would have to be taken into account as well and would greatly
complicate things.
It is always possible to do a "poor man"'s query cache with triggers..
which would just leave you with basically a materialized view.
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-09-27 18:31:09 | Re: best statistic target for boolean columns |
| Previous Message | Gaetano Mendola | 2004-09-27 18:09:46 | best statistic target for boolean columns |