X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 673419FCF40 for ; Mon, 28 Aug 2006 11:17:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 65802-06 for ; Mon, 28 Aug 2006 14:17:54 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by postgresql.org (Postfix) with ESMTP id 9C56C9FCF3E for ; Mon, 28 Aug 2006 11:17:53 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id p77so1340329nfc for ; Mon, 28 Aug 2006 07:17:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sA8ZftwK6OnkmFt5hup9LoGAvrIKQ2er7uhDF/HOiu58JETa64qT99YrN9dtlmMCFdH+bP5wsMnpf+I5/3EUZ4SfdSmGBGgy/D36+qj2eZJnvtHXOyNUVsdLtbg+xpSkr2y7dL6sJJCy5YdBz6j3XO8M9ijrMJ6ZTKQTV2g1fKU= Received: by 10.65.157.13 with SMTP id j13mr6914480qbo; Mon, 28 Aug 2006 07:17:51 -0700 (PDT) Received: by 10.64.27.7 with HTTP; Mon, 28 Aug 2006 07:17:51 -0700 (PDT) Message-ID: Date: Mon, 28 Aug 2006 14:17:51 +0000 From: "Christopher Browne" To: "Ravindran G - TLS, Chennai." , pgsql-performance@postgresql.org Subject: Re: Postgre SQL 7.1 cygwin performance issue. In-Reply-To: <012301731C23DE4DBFE035647C68F1CC03BE0092@sindhu.ctd.hcltech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <012301731C23DE4DBFE035647C68F1CC03BE0092@sindhu.ctd.hcltech.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.199 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/432 X-Sequence-Number: 20617 On 8/28/06, Ravindran G - TLS, Chennai. wrote: > Thanks Alvaro. > > We are using PostgreSQL 7.1 cygwin installed on Windows 2000. > > We understand that the maximum connections that can be set is 64 in > Postgresql 7.1 version. > > But our application is installed in 8 / 10 PC or more than that and it op= ens > multiple connections and it exceeds 64. > > Because of this the subsequent connections are failed to connect with DB > from application. > > Please advise us on how to resolve this ?. I don't think you have any answer other than to migrate to a better-supportable version of PostgreSQL. The last release of 7.1 was in August 2001; you're using a version that is now over five years old, with known "it'll eat your data" problems. That is why there have been some fifty-odd subsequent releases. The right answer is to arrange for an upgrade to a much less antiquated ver= sion. You're going to be pretty well restricted to the 64 connections until you upgrade to a more recent version. There is an alternative: You could migrate to some Unix-like platform (such as Linux or FreeBSD) where version 7.1.3 could in fact support more than 64 connections. --=20 http://www3.sympatico.ca/cbbrowne/linux.html Oddly enough, this is completely standard behaviour for shells. This is a roundabout way of saying `don't use combined chains of `&&'s and `||'s unless you think G=F6del's theorem is for sissies'.