Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e7SHR1C46482 for ; Mon, 28 Aug 2000 13:27:01 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id NAA16524; Mon, 28 Aug 2000 13:26:22 -0400 (EDT) To: Pierre Padovani cc: pierre@kahuna.versions.com, pgsql-sql@postgresql.org Subject: Re: shared memory leak in 7.0.2? In-reply-to: <39AA7EEA.8D4E2FA7@tivoli.com> References: <20000826221523.15597.qmail@kahuna.versions.com> <12490.967471440@sss.pgh.pa.us> <39AA7EEA.8D4E2FA7@tivoli.com> Comments: In-reply-to Pierre Padovani message dated "Mon, 28 Aug 2000 10:02:02 -0500" Date: Mon, 28 Aug 2000 13:26:22 -0400 Message-ID: <16521.967483582@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/309 Pierre Padovani writes: > Here is the current output of that ipc command: Looks pretty reasonable --- the three shmem segments look to be about what postgres should be using (I take it you've got -B set to 350 or so). > If postgres were to crash for some reason. Would the shared memory be > left in never never land? In theory the postmaster should release those segments when it's shut down, or failing that reuse 'em when it's restarted. We have heard occasional reports of this failing to happen on some platforms; but again, unless you're restarting the postmaster on a regular basis that doesn't seem like it'd be the issue. Anyway, keep an eye on things with ipcs and we'll see what's going on... regards, tom lane