From: kmh496 <kmh496@kornet.net>
To: pgsql-php@postgresql.org
Subject: Re: server dropping connection
Date: Wed, 03 May 2006 18:14:45 +0900
Message-ID: <1146647685.28587.1.camel@var.sirfsup.com> (raw)
In-Reply-To: <1146615164403774.2.ppp8@ppp8>
References: <1146615164403774.2.ppp8@ppp8>
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 <a href="http://www.myowndictionary.com">myowndictionary</a; was
made to help students of many languages learn them faster.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: kmh496@kornet.net
Subject: Re: server dropping connection
In-Reply-To: <1146647685.28587.1.camel@var.sirfsup.com>
References: <1146615164403774.2.ppp8@ppp8> <1146647685.28587.1.camel@var.sirfsup.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox