| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Michael Nolan <htfoot(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Are there tuning parameters that don't take effect immediately? |
| Date: | 2015-06-12 21:00:28 |
| Message-ID: | 557B486C.1030207@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 06/12/2015 01:37 PM, Michael Nolan wrote:
> Last night I was doing some tuning on a database The longest query I
> was running was taking around 160 seconds. I didn't see much change in
> the running time for that query, even after restarting PG.
>
> Today, with roughly the same system load (possibly even a bit heavier
> load), that query is running about 40 seconds.
Sounds like some of the relations are cached versus not.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Nolan | 2015-06-12 21:13:49 | Re: Are there tuning parameters that don't take effect immediately? |
| Previous Message | David G. Johnston | 2015-06-12 20:52:33 | Re: Are there tuning parameters that don't take effect immediately? |