From: | "Matthew Dennis" <mdennis(at)merfer(dot)net> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | david(at)lang(dot)hm, "Matthew Wakeling" <matthew(at)flymine(dot)org>, "PostgreSQL Performance" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception |
Date: | 2008-08-29 01:53:32 |
Message-ID: | e94d85500808281853g22f67274pc9b4c5e3b30bb05a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Aug 28, 2008 at 8:11 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> > wait a min here, postgres is supposed to be able to survive a complete
> box
> > failure without corrupting the database, if killing a process can corrupt
> > the database it sounds like a major problem.
>
> Yes it is a major problem, but not with postgresql. It's a major
> problem with the linux OOM killer killing processes that should not be
> killed.
>
> Would it be postgresql's fault if it corrupted data because my machine
> had bad memory? Or a bad hard drive? This is the same kind of
> failure. The postmaster should never be killed. It's the one thing
> holding it all together.
>
I fail to see the difference between the OOM killing it and the power going
out. And yes, if the power went out and PG came up with a corrupted DB
(assuming I didn't turn off fsync, etc) I *would* blame PG. I understand
that killing the postmaster could stop all useful PG work, that it could
cause it to stop responding to clients, that it could even "crash" PG, et
ceterabut if a particular process dying causes corrupted DBs, that sounds
borked to me.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-08-29 02:01:53 | Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception |
Previous Message | Scott Marlowe | 2008-08-29 01:52:00 | Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception |