pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew Dennis <mdennis@merfer.net>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: david@lang.hm, "Matthew Wakeling" <matthew@flymine.org>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date: Thu, 28 Aug 2008 20:53:32 -0500
Message-ID: <e94d85500808281853g22f67274pc9b4c5e3b30bb05a@mail.gmail.com> (raw)
In-Reply-To: <dcc563d10808281811t5c98dcaexd98c5cfe679f428d@mail.gmail.com>
References: <BAY124-W57D3654AF1159CAF8EAC19F5660@phx.gbl>
	<alpine.DEB.1.10.0808271436210.907@asgard.lang.hm>
	<alpine.DEB.1.10.0808281411220.4454@aragorn.flymine.org>
	<EADBB336-A14E-492C-A8CA-105C8F77A43A@blighty.com>
	<alpine.DEB.1.10.0808281702450.4454@aragorn.flymine.org>
	<48B6EA7E.2090707@emolecules.com>
	<alpine.DEB.1.10.0808282110140.4454@aragorn.flymine.org>
	<dcc563d10808281542u383808bci4874713a31bd1cc6@mail.gmail.com>
	<alpine.DEB.1.10.0808281602460.2713@asgard.lang.hm>
	<dcc563d10808281811t5c98dcaexd98c5cfe679f428d@mail.gmail.com>

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.

view thread (65+ messages)  latest in thread

Message-ID: <e94d85500808281853g22f67274pc9b4c5e3b30bb05a@mail.gmail.com>
Permalink:  ../e94d85500808281853g22f67274pc9b4c5e3b30bb05a@mail.gmail.com/
Also on:    postgresql.org/message-id/e94d85500808281853g22f67274pc9b4c5e3b30bb05a@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: mdennis@merfer.net, scott.marlowe@gmail.com, matthew@flymine.org
  Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  In-Reply-To: <e94d85500808281853g22f67274pc9b4c5e3b30bb05a@mail.gmail.com>
  References: <BAY124-W57D3654AF1159CAF8EAC19F5660@phx.gbl> <alpine.DEB.1.10.0808271436210.907@asgard.lang.hm> <alpine.DEB.1.10.0808281411220.4454@aragorn.flymine.org> <EADBB336-A14E-492C-A8CA-105C8F77A43A@blighty.com> <alpine.DEB.1.10.0808281702450.4454@aragorn.flymine.org> <48B6EA7E.2090707@emolecules.com> <alpine.DEB.1.10.0808282110140.4454@aragorn.flymine.org> <dcc563d10808281542u383808bci4874713a31bd1cc6@mail.gmail.com> <alpine.DEB.1.10.0808281602460.2713@asgard.lang.hm> <dcc563d10808281811t5c98dcaexd98c5cfe679f428d@mail.gmail.com> <e94d85500808281853g22f67274pc9b4c5e3b30bb05a@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox