X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 17619D1B437 for ; Thu, 13 May 2004 00:47:30 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 72430-01 for ; Thu, 13 May 2004 00:47:08 -0300 (ADT) Received: from mammoth.utopiasystems.net (meridian1.utopiasystems.net [66.150.45.40]) by svr1.postgresql.org (Postfix) with ESMTP id E6A41D1E34D for ; Thu, 13 May 2004 00:47:06 -0300 (ADT) Received: from [192.168.1.100] ([64.168.29.85]) by mammoth.utopiasystems.net with Microsoft SMTPSVC(6.0.3790.0); Wed, 12 May 2004 23:45:54 -0400 User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Wed, 12 May 2004 17:15:43 -0700 Subject: Re: RAM usage per connection From: Steve Lane To: Tom Lane Cc: Message-ID: In-Reply-To: <28150.1084392817@sss.pgh.pa.us> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 13 May 2004 03:45:55.0109 (UTC) FILETIME=[CB5C3D50:01C4389C] X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.8 tagged_above=0.0 required=5.0 tests=DATE_IN_PAST_03_06, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200405/121 X-Sequence-Number: 13437 > From: Tom Lane > Date: Wed, 12 May 2004 16:13:37 -0400 > To: Steve Lane > Cc: pgsql-admin@postgresql.org > Subject: Re: [ADMIN] RAM usage per connection > > Steve Lane writes: >> I have a customer with an application in production (postgres + php + >> apache) where we began seeing a number of scary messages in the logs. (It's >> postgres 7.2.1, by the way). > ^^^^^^^^^^^^^^ > > Reading the CVS logs for post-7.2.1 bug fixes will curl your toes. > You're irresponsible to still be running production data on that > version. Move up to 7.2.4 before you find out the hard way. I spoke too hastily. It's 7.1.3. Which probably doesn't make it better :-( > >> I tried increasing max_clients, but got a message to the effect that SHMMIN >> was set incorrectly on my machine ... > > I'd expect SHMMAX to be the issue not SHMMIN. It's set very > conservatively on many platforms, and you should not be afraid to raise > it. I was also puzzled to see the reference to SHMMIN. I'll look again. -- steve