| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Luke Lonergan" <LLonergan(at)greenplum(dot)com> |
| Cc: | "david(at)lang(dot)hm" <david(at)lang(dot)hm>, "glynastill(at)yahoo(dot)co(dot)uk" <glynastill(at)yahoo(dot)co(dot)uk>, "rjpeace(at)earthlink(dot)net" <rjpeace(at)earthlink(dot)net>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: understanding postgres issues/bottlenecks |
| Date: | 2009-01-11 23:44:53 |
| Message-ID: | dcc563d10901111544l3d039a22l7132064338016ad@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, Jan 11, 2009 at 4:16 PM, Luke Lonergan <LLonergan(at)greenplum(dot)com> 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.
I've been using pgsql since way back, in a lot of projects, and almost
almost of them on some flavor of linux, usually redhat. I have had
zero kernel crashes on production dbs in that time. I'd be interested
to know which historic kernels caused you the crashes.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M. Edward (Ed) Borasky | 2009-01-12 02:43:42 | Re: understanding postgres issues/bottlenecks |
| Previous Message | david | 2009-01-11 23:35:22 | Re: understanding postgres issues/bottlenecks |