From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Runtime variations during day |
Date: | 2013-02-13 22:34:37 |
Message-ID: | 1360794877.18626.YahooMailNeo@web162906.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> wrote:
> Anyway it does not seam related to statistics as the query plan
> is exactly the same for both scenarios, morning and evening:
> Morning:
> Index Scan using pagpk_aux_mes, pagpk_aux_mes, pk_cadpag,
> pk_cadpag, pk_cadpag, pagchavefunc00 on cadpag
> Evening:
> Seq Scan on cadpag
Those don't look exactly the same to me.
> I've used this query just as an example but the general feeling
> is that everything takes more time to process in the evening.
> Evening is also the period with more tasks in the the database.
Well, if the resources are split among more processes, each process
will take longer to run. No surprise there. Of course, there
could be some interaction -- queries which do more work because
statistics are out of date could contribute to the slowdown of
everything else.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrízio de Royes Mello | 2013-02-13 22:44:12 | Re: Runtime variations during day |
Previous Message | Alvaro Herrera | 2013-02-13 22:32:55 | Re: Runtime variations during day |