| From: | Jeff <threshar(at)torgo(dot)978(dot)org> |
|---|---|
| To: | M(dot) Edward (Ed) Borasky <znmeb(at)cesmail(dot)net> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: understanding postgres issues/bottlenecks |
| Date: | 2009-01-13 13:40:32 |
| Message-ID: | C7C2370D-D984-4ABC-8C38-7316E192A083@torgo.978.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Jan 11, 2009, at 9:43 PM, M. Edward (Ed) Borasky wrote:
> Luke Lonergan wrote:
>> Not to mention the #1 cause of server faults in my experience: OS
>> kernel bug causes a crash. Battery backup doesn't help you much
>> there.
>
Not that long ago (a month or so) we ran into a problem where hpacucli
(Utility for configuring/inspecting/etc HP smartarray controllers)
would tickle the cciss driver in such a way that it would cause a
kernel panic. KABLAMMO (No data loss! weeeee!). The box had run for
a long time without crashes, but it seems that when we added more
disks and started the array building the new logical drive some
magical things happened.
Bugs happen. The [bad word] of it is catching the culprit with its
fingers in the cookie jar.
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-01-13 15:40:35 | Re: dbt-2 tuning results with postgresql-8.3.5 |
| Previous Message | Bill Preston | 2009-01-13 06:13:44 | Re: Slow insert performace, 8.3 Wal related? |