X-Original-To: pgsql-hackers@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id AF54C475C8B for ; Tue, 11 Feb 2003 13:55:47 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 00CF4475C5F for ; Tue, 11 Feb 2003 13:55:47 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1BItT5u027233; Tue, 11 Feb 2003 13:55:30 -0500 (EST) To: "scott.marlowe" Cc: PostgresSQL Hackers Mailing List Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy] In-reply-to: References: Comments: In-reply-to "scott.marlowe" message dated "Tue, 11 Feb 2003 11:34:32 -0700" Date: Tue, 11 Feb 2003 13:55:29 -0500 Message-ID: <27232.1044989729@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/411 X-Sequence-Number: 35353 "scott.marlowe" writes: > Is setting the max connections to something like 200 reasonable, or likely > to cause too many problems? That would likely run into number-of-semaphores limitations (SEMMNI, SEMMNS). We do not seem to have as good documentation about changing that as we do about changing the SHMMAX setting, so I'm not sure I want to buy into the "it's okay to expect people to fix this before they can start Postgres the first time" argument here. Also, max-connections doesn't silently skew your testing: if you need to raise it, you *will* know it. regards, tom lane