Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7BA4365030F for ; Thu, 28 Aug 2008 22:53:37 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 50045-02-4 for ; Thu, 28 Aug 2008 22:53:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by postgresql.org (Postfix) with ESMTP id 16A2B650311 for ; Thu, 28 Aug 2008 22:53:33 -0300 (ADT) Received: by wf-out-1314.google.com with SMTP id 25so601197wfc.28 for ; Thu, 28 Aug 2008 18:53:32 -0700 (PDT) Received: by 10.142.201.3 with SMTP id y3mr761758wff.5.1219974812277; Thu, 28 Aug 2008 18:53:32 -0700 (PDT) Received: by 10.142.44.17 with HTTP; Thu, 28 Aug 2008 18:53:32 -0700 (PDT) Message-ID: Date: Thu, 28 Aug 2008 20:53:32 -0500 From: "Matthew Dennis" To: "Scott Marlowe" Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Cc: david@lang.hm, "Matthew Wakeling" , "PostgreSQL Performance" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_604_14965551.1219974812263" References: <48B6EA7E.2090707@emolecules.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200808/404 X-Sequence-Number: 31285 ------=_Part_604_14965551.1219974812263 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Aug 28, 2008 at 8:11 PM, Scott Marlowe 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. ------=_Part_604_14965551.1219974812263 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On Thu, Aug 28, 2008 at 8:11 PM, Scott Marlowe <scott.marlowe@gmail.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.
------=_Part_604_14965551.1219974812263--