Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VbotZ-0008Mx-LV for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Oct 2013 09:50:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VbotZ-0004Sk-44 for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Oct 2013 09:50:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VbotX-0004Sa-RS for pgsql-hackers@postgresql.org; Thu, 31 Oct 2013 09:50:27 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VbotU-0007kR-JX for pgsql-hackers@postgresql.org; Thu, 31 Oct 2013 09:50:27 +0000 Received: from intern.anarazel.de (p5DDC6F4C.dip0.t-ipconnect.de [93.220.111.76]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 8D2664E8002; Thu, 31 Oct 2013 10:50:22 +0100 (CET) Date: Thu, 31 Oct 2013 10:50:21 +0100 From: Andres Freund To: Heikki Linnakangas Cc: Robert Haas , Tom Lane , Andrew Dunstan , "pgsql-hackers@postgresql.org" Subject: Re: Something fishy happening on frogmouth Message-ID: <20131031095021.GA31628@alap2.anarazel.de> References: <6557.1383073940@sss.pgh.pa.us> <27889.1383139602@sss.pgh.pa.us> <20131030133718.GB11429@awork2.anarazel.de> <28492.1383140966@sss.pgh.pa.us> <527223E8.2020207@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <527223E8.2020207@vmware.com> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Hi, On 2013-10-31 11:33:28 +0200, Heikki Linnakangas wrote: > Wait, that sounds horrible. If you kill -9 the server, and then rm -rf > $PGDATA, the shared memory segment is leaked until next reboot? I find that > unacceptable. There are many scenarios where you never restart postmaster > after a crash. For example, if you have an automatic failover setup; you > fail over to the standby in case of crash, and re-initialize the old master > with e.g rsync. Our main shared memory segment works the same way, doesn't it? And it has for a long time. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers