X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B62803A42F3 for ; Wed, 1 Dec 2004 17:41:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 99113-10 for ; Wed, 1 Dec 2004 17:41:25 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E14BE3A5618 for ; Wed, 1 Dec 2004 17:41:24 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iB1HfOKP013532; Wed, 1 Dec 2004 12:41:24 -0500 (EST) To: postgresql@thomasbache.de Cc: pgsql-admin@postgresql.org Subject: Re: "too many clients" and no cure In-reply-to: <20041201172005.738A26EC191@digi1.shellsystem.de> References: <20041201172005.738A26EC191@digi1.shellsystem.de> Comments: In-reply-to postgresql@thomasbache.de message dated "Wed, 01 Dec 2004 18:20:05 +0100" Date: Wed, 01 Dec 2004 12:41:23 -0500 Message-ID: <13531.1101922883@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/22 X-Sequence-Number: 15608 postgresql@thomasbache.de writes: >> It sounds like you forgot to restart the postmaster after changing >> postgresql.conf. This is one of the parameters that is frozen at >> server start ... > No, I did restart the postmaster. Actually more than once. In that case, maybe you edited the wrong copy of postgresql.conf? Try checking "SHOW max_connections" to verify what the postmaster thinks the value is. > I do not have to restart the server after changing kernel parameters > with sysctl, do I? I don't think kernel limits would lead to "too many clients" --- you'd be getting different sorts of failures if the problem were in that area. regards, tom lane