Received: from serv1.ilse.nl (serv1.ilse.nl [212.189.131.11]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAOJn3A57789 for ; Fri, 24 Nov 2000 14:49:03 -0500 (EST) (envelope-from mathijs@ilse.nl) Received: (from mathijs@localhost) by serv1.ilse.nl (8.11.0/8.10.2) id eAOJn4973698 for pgsql-sql@postgresql.org; Fri, 24 Nov 2000 20:49:04 +0100 (MET) Date: Fri, 24 Nov 2000 20:49:04 +0100 From: Mathijs Brands To: pgsql-sql@postgresql.org Subject: Re: problems with postmaster Message-ID: <20001124204904.B73589@ilse.nl> References: <20001124181226.15192.qmail@nwcst294> <20001124123429.A22742@thune.mrc-home.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001124123429.A22742@thune.mrc-home.org>; from dalgoda@ix.netcom.com on Fri, Nov 24, 2000 at 12:34:29PM -0600 X-Unexpected-Header: The Spanish Inquisition X-Archive-Number: 200011/226 X-Sequence-Number: 257 On Fri, Nov 24, 2000 at 12:34:29PM -0600, Mike Castle allegedly wrote: > ipcclean > pg_ctl stop > > Though finding out about ipcclean was not easy considering the output > given. There is no mention of it in any of the FAQs. > > mrc You could also use ipcrm manually to clean up the shm segments postgresql left lying around. Moral of the story: DON'T USE A SIGKILL TO STOP POSTGRESQL. Of course, there are times when you need to be somewhat crude. Mathijs -- It's not that perl programmers are idiots, it's that the language rewards idiotic behavior in a way that no other language or tool has ever done. Erik Naggum