Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA62478 for ; Wed, 17 Nov 1999 00:06:35 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id AAA24413; Wed, 17 Nov 1999 00:05:27 -0500 (EST) To: "Hamid Khoshnevis" cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] zombie postmasters In-reply-to: Your message of Tue, 16 Nov 1999 15:06:35 -0800 <000201bf3087$3afadae0$810a0a0a@hamid.emarq> Date: Wed, 17 Nov 1999 00:05:27 -0500 Message-ID: <24411.942815127@sss.pgh.pa.us> From: Tom Lane "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? regards, tom lane