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 6E850D1B46A for ; Wed, 14 Jan 2004 12:47:46 +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 98223-03 for ; Wed, 14 Jan 2004 08:47:17 -0400 (AST) Received: from quasar.skima.is (quasar.skima.is [212.30.200.205]) by svr1.postgresql.org (Postfix) with ESMTP id C9D8CD1B441 for ; Wed, 14 Jan 2004 08:47:13 -0400 (AST) Received: from physicallink.com ([194.144.34.89] [194.144.34.89]) by quasar.skima.is with ESMTP; Wed, 14 Jan 2004 12:47:12 Z Message-Id: <40053A91.5060001@physicallink.com> Date: Wed, 14 Jan 2004 12:48:17 +0000 From: =?ISO-8859-1?Q?J=F3n_Ragnarsson?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; is-IS; rv:1.5) Gecko/20031007 X-Accept-Language: is, en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: 100 simultaneous connections, critical limit? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/137 X-Sequence-Number: 5312 I am writing a website that will probably have some traffic. Right now I wrap every .php page in pg_connect() and pg_close(). Then I read somewhere that Postgres only supports 100 simultaneous connections (default). Is that a limitation? Should I use some other method when writing code for high-traffic website? J.