From: | Herouth Maoz <herouth(at)unicell(dot)co(dot)il> |
---|---|
To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Slow update |
Date: | 2009-02-09 15:39:37 |
Message-ID: | 49904E39.1080203@unicell.co.il |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Grzegorz Jaśkiewicz wrote:
> On Mon, Feb 9, 2009 at 12:50 PM, Herouth Maoz <herouth(at)unicell(dot)co(dot)il> wrote:
>
>> I hope someone can clue me in based on the results of explain analyze.
>>
>
> Did you have a chance to run vmstat on it, and post it here ? Maybe -
> if db resides on the same disc with everything else, something
> (ab)uses that much io, and it has to wait.
I haven't ran it, but it's worth mentioning that the data is on a
separate device than the system/users. Also, the system is used only for
the reporting system. Other than PostgreSQL and the cron job that runs
this query, nothing runs on the system at night. Reports start being
produced around 7:00 AM which should give the query ample time to finish
(almost 3 hours) before any contention starts.
Herouth
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-09 15:47:15 | Re: Out of memory on SELECT in 8.3.5 |
Previous Message | Raymond O'Donnell | 2009-02-09 14:29:27 | Re: Strange thing happened when upgrading postgres on windows on my laptop |