X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 633A59FB2D5 for ; Thu, 10 Aug 2006 00:38:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 74409-03 for ; Thu, 10 Aug 2006 00:38:33 -0300 (ADT) 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 5EC369FB315 for ; Thu, 10 Aug 2006 00:38:32 -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 k7A3caCW021940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Aug 2006 20:38:37 -0700 Message-ID: <44DAAA38.2070300@commandprompt.com> Date: Wed, 09 Aug 2006 20:38:32 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: "Joshua D. Drake" CC: PostgreSQL-development Subject: Re: Win32 max connections bug (causing crashes) References: <44DA6CF6.8020201@commandprompt.com> In-Reply-To: <44DA6CF6.8020201@commandprompt.com> 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 20:38:37 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.185 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200608/681 X-Sequence-Number: 88174 Joshua D. Drake wrote: > 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. Further on this with Debug 5: Client: DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 19299/1/0, nestlvl: 1, children: <> DEBUG: CommitTransaction DEBUG: name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 19299/1/0, nestlvl: 1, children: <> DEBUG: StartTransactionCommand DEBUG: StartTransaction DEBUG: name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 19300/1/0, nestlvl: 1, children: <> DEBUG: ProcessUtility DEBUG: CommitTransactionCommand DEBUG: CommitTransaction DEBUG: name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 19300/1/0, nestlvl: 1, children: <> Connection to database 'bench' failed. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. jd@scratch:/usr/local/pgsql/bin$ Server to follow in next message. Joshua D. Drake > > 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/