X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 43B00D1D8D2 for ; Wed, 14 Jan 2004 15:05:22 +0000 (GMT) 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 25481-07 for ; Wed, 14 Jan 2004 11:04:54 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 2C09DD1DA66 for ; Wed, 14 Jan 2004 11:04:50 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0EF4rpH003598; Wed, 14 Jan 2004 10:04:53 -0500 (EST) To: Christopher Browne Cc: pgsql-performance@postgresql.org Subject: Re: 100 simultaneous connections, critical limit? In-reply-to: References: <40053A91.5060001@physicallink.com> Comments: In-reply-to Christopher Browne message dated "Wed, 14 Jan 2004 08:27:03 -0500" Date: Wed, 14 Jan 2004 10:04:53 -0500 Message-ID: <3597.1074092693@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/142 X-Sequence-Number: 5317 Christopher Browne writes: > Clinging to sanity, jonr@physicallink.com (Jón Ragnarsson) mumbled into her beard: >> Then I read somewhere that Postgres only supports 100 simultaneous >> connections (default). > I thought the out-of-the-box default was 32. Pre-7.4 it was 32; in 7.4 it's 100 (if your kernel settings will allow it). It's important to point out that both of these are trivial-to-alter configuration settings, not some kind of hardwired limit. However, the more backend processes you have, the more RAM you need on the database server. It's good advice to look into connection pooling instead of trying to push max_connections up to the moon. regards, tom lane