X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 3FD5E9FB2D6 for ; Wed, 9 Aug 2006 20:17:20 -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 50145-03 for ; Wed, 9 Aug 2006 23:17:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 89A809FB2D5 for ; Wed, 9 Aug 2006 20:17:11 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id k79NHDPb016968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 9 Aug 2006 16:17:14 -0700 Message-ID: <44DA6CF6.8020201@commandprompt.com> Date: Wed, 09 Aug 2006 16:17:10 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: PostgreSQL-development Subject: Win32 max connections bug (causing crashes) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 09 Aug 2006 16:17:14 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200608/656 X-Sequence-Number: 88149 Hello, I had a customer call in today they are running Win2003 with 22 gig of ram (that may be a mistype on their end, it may be 32gigs of ram). They cranked up their postgresql max_connections to 500. When PostgreSQL hits above 400, it dies and I don't mean a slow crawl type death. A death where all connections close and the database does a rollback and restart. I was able to reproduce with a simple pgbench on my own win32 environment. I wasn't able to go above 300 with mine. Any thoughts? Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/