| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | William Yu <wyu(at)talisys(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Caching of Queries |
| Date: | 2004-10-02 22:50:58 |
| Message-ID: | 200410021550.58484.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
William,
> Just my 2 cents on this whole issue. I would lean towards having result
> caching in pgpool versus the main backend. I want every ounce of memory
> on a database server devoted to the database. Caching results would
> double the effect of cache flushing ... ie, now both the results and the
> pages used to build the results are in memory pushing out other stuff to
> disk that may be just as important.
>
> If it was in pgpool or something similar, I could devote a separate
> machine just for caching results leaving the db server untouched.
Oddly, Joe Conway just mentioned the same idea to me.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2004-10-02 23:20:41 | Re: inconsistent/weird index usage |
| Previous Message | Russell Smith | 2004-10-02 22:50:28 | Re: Query planner problem |