pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@2ndquadrant.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Something fishy happening on frogmouth
Date: Thu, 31 Oct 2013 10:50:21 +0100
Message-ID: <20131031095021.GA31628@alap2.anarazel.de> (raw)
In-Reply-To: <527223E8.2020207@vmware.com>
References: <6557.1383073940@sss.pgh.pa.us>
	<CA+Tgmob859sdnDuHAF31BE55qEoREnCzzWeqDbgkNB0d_F+zmA@mail.gmail.com>
	<27889.1383139602@sss.pgh.pa.us>
	<20131030133718.GB11429@awork2.anarazel.de>
	<28492.1383140966@sss.pgh.pa.us>
	<CA+TgmobOqYVBD=xdWHF12R4+dxeBDS3ruxware7ZWtD5mfSO5Q@mail.gmail.com>
	<527223E8.2020207@vmware.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

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



view thread (38+ messages)  latest in thread

Message-ID: <20131031095021.GA31628@alap2.anarazel.de>
Permalink:  ../20131031095021.GA31628@alap2.anarazel.de/
Also on:    postgresql.org/message-id/20131031095021.GA31628@alap2.anarazel.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: andres@2ndquadrant.com, hlinnakangas@vmware.com, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, andrew@dunslane.net
  Subject: Re: Something fishy happening on frogmouth
  In-Reply-To: <20131031095021.GA31628@alap2.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox