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 e7SE44L36440 for ; Mon, 28 Aug 2000 10:04:05 -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 KAA12493; Mon, 28 Aug 2000 10:04:01 -0400 (EDT) To: pierre@kahuna.versions.com cc: pgsql-sql@postgresql.org Subject: Re: shared memory leak in 7.0.2? In-reply-to: <20000826221523.15597.qmail@kahuna.versions.com> References: <20000826221523.15597.qmail@kahuna.versions.com> Comments: In-reply-to pierre@kahuna.versions.com message dated "Sat, 26 Aug 0100 15:15:23 -0700" Date: Mon, 28 Aug 2000 10:04:00 -0400 Message-ID: <12490.967471440@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/308 pierre@kahuna.versions.com writes: > i've been running 7.0.2 for the last month or so, and I've had to > reboot my redhat linux box twice to clear up a shared memory leak > issue. Essentially with the DB running for about 2weeks with large > amounts of usage, eventually the Os runs out of shared memory and the > db crashes and fails to restart. The only way to get the db back > online is to reboot. I haven't seen this reported before. Are you sure Postgres deserves the blame, rather than some other package? Postgres' use of shared memory is fixed for the life of a postmaster, so unless you're constantly restarting the postmaster I don't see how we could be leaking shmem. However, rather than speculate, let's get some hard facts. Try using "ipcs -m -a" to keep track of shared mem allocations, and see what usage is creeping up over time. regards, tom lane