| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Howard Cole" <howardnews(at)selestial(dot)com> |
| Cc: | "Teodor Sigaev" <teodor(at)sigaev(dot)ru>, "PgSql General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to reduce impact of a query. |
| Date: | 2008-11-17 15:28:45 |
| Message-ID: | dcc563d10811170728w2de23fd4u53a36d404a6bb72f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 17, 2008 at 8:17 AM, Howard Cole <howardnews(at)selestial(dot)com> wrote:
> Teodor Sigaev wrote:
>>>
>>> The machine in question is a 1GB Ram, AMD 64 with Raid 1 Sata disks. Non
Your entire disk io subsystem is a pair of hard drives. I'm assuming
software RAID.
> The time that this query takes is not the issue, rather it is the impact
> that it has on the server - effectively killing it for the 40 seconds due to
> the heavy disk access.
You either need to invest more into your drive subsystem so it can
handle parallel load better, or you need to create a slave db with
slony or londiste so that the ugly queries hit the slave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Howard Cole | 2008-11-17 15:42:18 | Re: How to reduce impact of a query. |
| Previous Message | Howard Cole | 2008-11-17 15:17:40 | Re: How to reduce impact of a query. |