From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pierre Padovani <ppadovan@tivoli.com>
Cc: pierre@kahuna.versions.com
Cc: pgsql-sql@postgresql.org
Subject: Re: shared memory leak in 7.0.2?
Date: Mon, 28 Aug 2000 13:26:22 -0400
Message-ID: <16521.967483582@sss.pgh.pa.us> (raw)
In-Reply-To: <39AA7EEA.8D4E2FA7@tivoli.com>
References: <20000826221523.15597.qmail@kahuna.versions.com>
<12490.967471440@sss.pgh.pa.us>
<39AA7EEA.8D4E2FA7@tivoli.com>
Pierre Padovani <ppadovan@tivoli.com> 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
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, ppadovan@tivoli.com, pierre@kahuna.versions.com
Subject: Re: shared memory leak in 7.0.2?
In-Reply-To: <16521.967483582@sss.pgh.pa.us>
References: <20000826221523.15597.qmail@kahuna.versions.com> <12490.967471440@sss.pgh.pa.us> <39AA7EEA.8D4E2FA7@tivoli.com> <16521.967483582@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