From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | tv(at)fuzzy(dot)cz |
Cc: | zz_11(at)mail(dot)bg, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: possible wrong query plan on pg 8.3.5, |
Date: | 2009-09-14 13:38:22 |
Message-ID: | 603c8f070909140638y1219101ckae5fc0bcac6d3cee@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
2009/9/14 <tv(at)fuzzy(dot)cz>:
> It seems there's something very wrong - the plans are "equal" but in the
> first case the results (actual time) are multiplied by 100. Eithere there
> is some sort of cache (so the second execution is much faster), or the
> system was busy during the first execution, or there is something wrong
> with the hardware.
I think you should run this query more than twice. If it's slow the
first time and fast every time for many executions after that, then
it's probably just the data getting loaded into the OS cache (or
shared buffers). If it's bouncing back and forth between fast and
slow, you might want to check whether your machine is swapping.
It might also be helpful to post all the uncommented settings from
your postgresql.conf file.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Andrzej Zawadzki | 2009-09-14 13:54:14 | CLUSTER and a problem |
Previous Message | zz_11 | 2009-09-14 10:49:39 | Re: possible wrong query plan on pg 8.3.5, |