From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Kavan, Dan (IMS) <KavanD@imsweb.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: memory allocation ; postgresql-8.0
Date: Thu, 12 May 2005 14:07:21 -0500
Message-ID: <1115924841.22291.5.camel@state.g2switchworks.com> (raw)
In-Reply-To: <782D2A81EC812642B857B03B506E0B4432648C@granite.omni.imsweb.com>
References: <782D2A81EC812642B857B03B506E0B4432648C@granite.omni.imsweb.com>
On Thu, 2005-05-12 at 12:46, Kavan, Dan (IMS) wrote:
> Do psql calls/procedures access resources reserved from the
> kernel.shmmax?
Only in the sense that it can execute a query, which in the backend
could therefore use shared memory. psql, itself, doesn't use shared
memory.
> How about the tar or copy sysadmin commands? I would guess they don't
> use kernel.shmmax resources.
Correct. Actually, very few types of programs use shared memory.
> Finally, work memory alos does not access
> resources reserved from kernel.shmmax, correct?
Correct. The only parts of postgresql.conf that affect shared memory
usage are max connections, shared buffers, and the fsm.
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-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, KavanD@imsweb.com
Subject: Re: memory allocation ; postgresql-8.0
In-Reply-To: <1115924841.22291.5.camel@state.g2switchworks.com>
References: <782D2A81EC812642B857B03B506E0B4432648C@granite.omni.imsweb.com> <1115924841.22291.5.camel@state.g2switchworks.com>
* 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