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 5446FD1E232 for ; Wed, 12 May 2004 17:14:00 -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 61867-03 for ; Wed, 12 May 2004 17:13:41 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id B5502D1E2D2 for ; Wed, 12 May 2004 17:13:38 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i4CKDbZU028151; Wed, 12 May 2004 16:13:37 -0400 (EDT) To: Steve Lane Cc: pgsql-admin@postgresql.org Subject: Re: RAM usage per connection In-reply-to: References: Comments: In-reply-to Steve Lane message dated "Wed, 12 May 2004 11:39:08 -0700" Date: Wed, 12 May 2004 16:13:37 -0400 Message-ID: <28150.1084392817@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/115 X-Sequence-Number: 13431 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 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. regards, tom lane