From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Eduardo Piombino <drakorg(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: a heavy duty operation on an "unused" table kills my server |
Date: | 2010-01-13 18:46:03 |
Message-ID: | 4B4E14EB.7080008@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Robert Haas wrote:
> I'm kind of surprised that there are disk I/O subsystems that are so
> bad that a single thread doing non-stop I/O can take down the whole
> server. Is that normal? Does it happen on non-Windows operating
> systems? What kind of hardware should I not buy to make sure this
> doesn't happen to me?
>
You can kill any hardware on any OS with the right abusive client.
Create a wide table and insert a few million records into it with
generate_series one day and watch what it does to queries trying to run
in parallel with that.
I think the missing step here to nail down exactly what's happening on
Eduardo's system is that he should open up some of the Windows system
monitoring tools, look at both disk I/O and CPU usage, and then watch
what changes when the troublesome ALTER TABLE shows up.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Eduardo Piombino | 2010-01-13 19:13:20 | Re: a heavy duty operation on an "unused" table kills my server |
Previous Message | Scott Marlowe | 2010-01-13 18:11:32 | Re: a heavy duty operation on an "unused" table kills my server |