Re: kill -KILL: What happens?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Florian Pflug <fgp(at)phlo(dot)org>, David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: kill -KILL: What happens?
Date: 2011-01-14 15:32:05
Message-ID: 1295018928-sup-8187@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Robert Haas's message of vie ene 14 00:03:53 -0300 2011:
> On Thu, Jan 13, 2011 at 8:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> > True.  It strikes me also that the postmaster does provide some services
> > other than accepting new connections:
> >
> > * ensuring that everybody gets killed if a backend crashes

> > While you could probably live without these in the scenario of "let my
> > honking big query finish before restarting", you would not want to do
> > without them in unattended operation.
>
> Yep. I'm pretty doubtful that you're going to want them even in that
> case, but you're surely not going to want them in unattended
> operation.

I'm sure you don't want that. The reason postmaster causes a restart of
all backends in case one of them crashes is that it could have left some
corrupted state behind. If postmaster dies, and then another backend
crashes, then your backend running "your honking big query" could run
across corrupted state and then you'd be in serious trouble.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2011-01-14 15:53:03 Re: Error code for "terminating connection due to conflict with recovery"
Previous Message Dimitri Fontaine 2011-01-14 15:31:28 Re: Add support for logging the current role