X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E28AF9FB2E8 for ; Wed, 3 May 2006 06:26:22 -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 33371-10 for ; Wed, 3 May 2006 06:13:55 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from relaygw2.kornet.net (relaygw2.kornet.net [61.74.75.197]) by postgresql.org (Postfix) with ESMTP id D96379FB2AF for ; Wed, 3 May 2006 06:13:21 -0300 (ADT) Received: from [211.48.62.137] ([211.48.62.137]) by relaygw2.kornet.net ([61.74.75.197]) with ESMTP id 2006050318:13:03:051221.26604.35220400 for ; Wed, 03 May 2006 18:13:03 +0900 (KST) Received: from [222.109.159.54] ([222.109.159.54]) by relay9.kornet.net ([211.48.62.137]) with ESMTP id 2006050318:13:21:760781.27312.229817264 for ; Wed, 03 May 2006 18:13:21 +0900 (KST) Subject: Re: server dropping connection From: kmh496 To: pgsql-php@postgresql.org In-Reply-To: <1146615164403774.2.ppp8@ppp8> References: <1146615164403774.2.ppp8@ppp8> Content-Type: text/plain; charset=EUC-KR Date: Wed, 03 May 2006 18:14:45 +0900 Message-Id: <1146647685.28587.1.camel@var.sirfsup.com> Mime-Version: 1.0 X-Mailer: Evolution 2.1.4 Content-Transfer-Encoding: 8bit X-TERRACE-SPAMMARK: NOT spam-marked. (by Terrace) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/2 X-Sequence-Number: 3502 2006-05-02 (È­), 18:13 -0600, Reed Loefgren ¾²½Ã±æ: > All, > > I've been trying to run a nested query via a browser using a php script. > The script looks at a table with a couple years worth of data (6M rows). > If I constrain the search to five or six days of the data it works fine > and displays the result set in the browser, but if I have it parse the > entire table it errors out with this message: > > server closed the connection unexpectedly This probably means the server > terminated abnormally before or while processing the request. > > The error points at line 33, which is the $query = "SELECT..." in the > script. > The full table query runs fine in psql and the very limited query runs > fine in the php script so I'm thinking there might be some type of > resource starvation or client connection timeout happening. In psql the > full query over two years of data returns a result set (limit 50) in about > three minutes. Any ideas where I should begin looking? > > thanks, http://httpd.apache.org/docs/1.3/mod/core.html#timeout says The TimeOut directive currently defines the amount of time Apache will wait for three things: 1. The total amount of time it takes to receive a GET request. 2. The amount of time between receipt of TCP packets on a POST or PUT request. 3. The amount of time between ACKs on transmissions of TCP packets in responses 4. > i am interested in what the change would be if you wrote a server-side function, however. > r > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings > > > -- my site myowndictionary was made to help students of many languages learn them faster.