From: Tom Lane <tgl@sss.pgh.pa.us>
To: pierre@kahuna.versions.com
Cc: pgsql-sql@postgresql.org
Subject: Re: shared memory leak in 7.0.2?
Date: Mon, 28 Aug 2000 10:04:00 -0400
Message-ID: <12490.967471440@sss.pgh.pa.us> (raw)
In-Reply-To: <20000826221523.15597.qmail@kahuna.versions.com>
References: <20000826221523.15597.qmail@kahuna.versions.com>
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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, pierre@kahuna.versions.com
Subject: Re: shared memory leak in 7.0.2?
In-Reply-To: <12490.967471440@sss.pgh.pa.us>
References: <20000826221523.15597.qmail@kahuna.versions.com> <12490.967471440@sss.pgh.pa.us>
* 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