X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id F22189FA38F for ; Tue, 13 Jun 2006 19:34:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 40530-07 for ; Tue, 13 Jun 2006 19:34:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id 867B89FA1A8 for ; Tue, 13 Jun 2006 19:34:12 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id k5DMY1LP043211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 13 Jun 2006 16:34:04 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.6/8.13.6) with ESMTP id k5DMY15X047590; Tue, 13 Jun 2006 16:34:01 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.6/8.13.6/Submit) id k5DMY1D5047589; Tue, 13 Jun 2006 16:34:01 -0600 (MDT) (envelope-from mfuhr) Date: Tue, 13 Jun 2006 16:34:01 -0600 From: Michael Fuhr To: Tom Lane Cc: mischa@ca.sophos.com, pgsql-performance@postgresql.org Subject: Re: Solaris shared_buffers anomaly? Message-ID: <20060613223401.GA47540@winnie.fuhr.org> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11046.1150237327@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/219 X-Sequence-Number: 19576 On Tue, Jun 13, 2006 at 06:22:07PM -0400, Tom Lane wrote: > Mischa Sandberg 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