Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.3/8.9.3) with SMTP id DAA92611 for ; Wed, 17 Nov 1999 03:35:14 -0500 (EST) (envelope-from wieck@debis.com) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgresql.org id m11o0QW-0003kLC; Wed, 17 Nov 99 09:26 MET Message-Id: From: wieck@debis.com (Jan Wieck) Subject: Re: [SQL] zombie postmasters To: tgl@sss.pgh.pa.us (Tom Lane) Date: Wed, 17 Nov 1999 09:26:52 +0100 (MET) Cc: hamid@emarq.com, pgsql-sql@postgresql.org Reply-To: wieck@debis.com (Jan Wieck) In-Reply-To: <24411.942815127@sss.pgh.pa.us> from "Tom Lane" at Nov 17, 99 00:05:27 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text > > "Hamid Khoshnevis" writes: > > In a web environment, a user can repeatedly starts and abort large queries > > which create a large number of zombie postmasters. > > It shouldn't be possible for there to be zombie postgres processes --- > the postmaster process should reap dead backends more or less instantly. > Either your postmaster is getting wedged somehow, or there is a > configure/install problem that has broken the postmaster's handling > of child-process exit. What platform are you using, exactly? What > if anything shows up in the postmaster log when this happens? No, Tom. It confused me too first. But with Zombie, he didn't meant what you and me think a Zombie is. And it aren't postmaster ones, it are regular backends that still run a huge query where the client is already gone. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #========================================= wieck@debis.com (Jan Wieck) #