Re: How to shoot yourself in the foot: kill -9 postmaster

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: How to shoot yourself in the foot: kill -9 postmaster
Date: 2001-03-06 03:12:00
Message-ID: 3AA4557F.875C6DFE@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Lamar Owen wrote:
> > Postmaster can easily enough find out if zombie backends are 'out there'
> > during startup, right?

> If you think it's easy enough, enlighten the rest of us ;-).

If postgres reported PGDATA on the command line it would be easy enough.

> > What can postmaster _do_ about it, though? It
> > won't necessarily be able to kill them -- but it also can't control
> > them. If it _can_ kill them, should it try?

> I think refusal to start is sufficient. They should go away by
> themselves as their clients disconnect, and forcing the issue doesn't

???? I have misunderstood your previous statement about not wanting to
force a manual crash recovery, then.

> > Should a set of backends detect a new postmaster coming up and try to
> > 'sync up' with that postmaster,

> Nice try ;-). How will you persuade the kernel that these processes are
> now children of the new postmaster?

Yeah, that's the kicker.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-03-06 03:17:36 Re: How to shoot yourself in the foot: kill -9 postmaster
Previous Message Tom Lane 2001-03-06 03:11:56 Re: How to shoot yourself in the foot: kill -9 postmaster