| From: | Erik Jones <ejones(at)engineyard(dot)com> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Taking the cache out of the equation? |
| Date: | 2009-06-12 22:12:57 |
| Message-ID: | 875976BE-CAC0-4F10-B7CC-0D651B109967@engineyard.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Jun 9, 2009, at 10:51 AM, Rob Sargent wrote:
> Caching helps a *lot* and I'm thankful for that but I would like to
> take it out of the picture as I massage my queries for better
> performance. Naturally the first invocation of the query cannot
> take advantage of the cache and these queries would normally only be
> called once for the same target data. What tricks are there to
> flush, ignore, circumvent the caching boost? (Especially in the
> production environment.)
Why on earth would you want your queries to always go to disk?
Erik Jones, Database Administrator
Engine Yard
Support, Scalability, Reliability
866.518.9273 x 260
Location: US/Pacific
IRC: mage2k
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-06-12 22:25:19 | Re: Taking the cache out of the equation? |
| Previous Message | Seb | 2009-06-12 21:35:09 | updateable/insertable view having left joined tables |