Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eADFZHs74834 for ; Mon, 13 Nov 2000 10:35:17 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eADFWbD09351; Mon, 13 Nov 2000 10:32:37 -0500 (EST) To: Michael Teter cc: rocael@usa.net, pgsql-sql@postgresql.org Subject: Re: shared memory problem In-reply-to: <20001113121743.87597.qmail@web10004.mail.yahoo.com> References: <20001113121743.87597.qmail@web10004.mail.yahoo.com> Comments: In-reply-to Michael Teter message dated "Mon, 13 Nov 2000 04:17:43 -0800" Date: Mon, 13 Nov 2000 10:32:37 -0500 Message-ID: <9348.974129557@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/91 X-Sequence-Number: 122 Michael Teter writes: > Perhaps there's some issue with the shared memory not > being freed quickly enough by the kernel? Never heard of that before. There is an issue with time delays on release of port addresses --- sometimes you may get a failure to bind() to a port address that was just released by a previous incarnation of the postmaster. But I haven't heard of such a thing for shared memory or semaphores. regards, tom lane