From: | Guido Neitzer <lists(at)event-s(dot)net> |
---|---|
To: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Slow Postgresql server |
Date: | 2007-04-12 14:08:03 |
Message-ID: | 16E9A17C-ADFA-43B2-B7EA-5C7A4D7E96D1@event-s.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches pgsql-performance |
On 12.04.2007, at 07:26, Ron wrote:
> You need to buy RAM and HD.
Before he does that, wouldn't it be more useful, to find out WHY he
has so much IO?
Have I missed that or has nobody suggested finding the slow queries
(when you have much IO on them, they might be slow at least with a
high shared memory setting).
So, my first idea is, to turn on query logging for queries longer
than a xy milliseconds, "explain analyse" these queries and see
wether there are a lot of seq scans involved, which would explain the
high IO.
Just an idea, perhaps I missed that step in that discussion
somewhere ...
But yes, it might also be, that the server is swapping, that's
another thing to find out.
cug
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2007-04-12 14:08:11 | Re: Benchmarking tools for the Postgres, EDB and Oracle Database |
Previous Message | Alvaro Herrera | 2007-04-12 14:07:22 | Re: What tools do people use to hack on PostgreSQL? |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-04-12 14:58:16 | Re: autovacuum multiworkers, patch 5 |
Previous Message | Tom Lane | 2007-04-12 13:29:52 | Re: [HACKERS] Fix mdsync never-ending loop problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2007-04-12 14:59:10 | Re: Slow Postgresql server |
Previous Message | Merlin Moncure | 2007-04-12 13:42:03 | Re: Large objetcs performance |