Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VdLjC-0001NI-Cs for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Nov 2013 15:06:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VdLjB-0003Pp-L4 for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Nov 2013 15:06:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VdLjA-0003Ph-Pl for pgsql-hackers@postgresql.org; Mon, 04 Nov 2013 15:06:04 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VdLj7-00088L-85 for pgsql-hackers@postgresql.org; Mon, 04 Nov 2013 15:06:04 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id rA4F5sM7011703; Mon, 4 Nov 2013 10:05:54 -0500 From: Tom Lane To: Andres Freund cc: Heikki Linnakangas , Noah Misch , Robert Haas , Andrew Dunstan , "pgsql-hackers@postgresql.org" Subject: Re: Something fishy happening on frogmouth In-reply-to: <20131104111912.GD17233@awork2.anarazel.de> References: <20131031095021.GA31628@alap2.anarazel.de> <22875.1383229757@sss.pgh.pa.us> <5272EC6A.2020004@vmware.com> <20131101162230.GA649568@tornado.leadboat.com> <52775A83.7090206@vmware.com> <20131104095521.GI3567@awork2.anarazel.de> <52778157.9050907@vmware.com> <20131104111912.GD17233@awork2.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 04 Nov 2013 12:19:12 +0100" Date: Mon, 04 Nov 2013 10:05:54 -0500 Message-ID: <11702.1383577554@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Andres Freund writes: > On 2013-11-04 13:13:27 +0200, Heikki Linnakangas wrote: >> On 04.11.2013 11:55, Andres Freund wrote: >>> Also, I don't think it's portable across platforms to access segments >>> that already have been unlinked. >> See >> http://pubs.opengroup.org/onlinepubs/009695299/functions/shm_unlink.html: >> "If one or more references to the shared memory object exist when the object >> is unlinked, the name shall be removed before shm_unlink() returns, but the >> removal of the memory object contents shall be postponed until all open and >> map references to the shared memory object have been removed." > We also support sysv shmem and have the same cleanup problem there. And what about Windows? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers