From: Michael Fuhr <mike@fuhr.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: mischa@ca.sophos.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Solaris shared_buffers anomaly?
Date: Tue, 13 Jun 2006 16:34:01 -0600
Message-ID: <20060613223401.GA47540@winnie.fuhr.org> (raw)
In-Reply-To: <11046.1150237327@sss.pgh.pa.us>
References: <1150151282.14661.42.camel@tigger>
<20060613000441.GI8588@kenobi.snowman.net>
<20060613200810.GZ34196@pervasive.com>
<448F3A6E.6080908@ca.sophos.com>
<11046.1150237327@sss.pgh.pa.us>
On Tue, Jun 13, 2006 at 06:22:07PM -0400, Tom Lane wrote:
> Mischa Sandberg <mischa@ca.sophos.com> writes:
> > vmstat showed that it was swapping like crazy.
> > Dropped shared_buffers back down again.
> > Swapping stopped.
>
> Does Solaris have any call that allows locking a shmem segment in RAM?
The Solaris 9 shmctl manpage mentions this token:
SHM_LOCK
Lock the shared memory segment specified by shmid in
memory. This command can be executed only by a process
that has an effective user ID equal to super-user.
--
Michael Fuhr
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mike@fuhr.org, tgl@sss.pgh.pa.us, mischa@ca.sophos.com
Subject: Re: Solaris shared_buffers anomaly?
In-Reply-To: <20060613223401.GA47540@winnie.fuhr.org>
* 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