Received: from Morgoth.esiway.net (Morgoth.esiway.net [193.194.16.157]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0LAM2V88491 for ; Mon, 21 Jan 2002 05:22:05 -0500 (EST) (envelope-from marco@esi.it) Received: from Megathlon.ESI (Ghost.esi.it [193.194.16.225]) by Morgoth.esiway.net (8.9.3/8.9.3) with ESMTP id LAA03725; Mon, 21 Jan 2002 11:21:46 +0100 Received: from there (Frodo.ESI [10.10.10.13]) by Megathlon.ESI (8.11.5/8.11.5) with SMTP id g0LALjR09061; Mon, 21 Jan 2002 11:21:45 +0100 Message-Id: <200201211021.g0LALjR09061@Megathlon.ESI> Content-Type: text/plain; charset="iso-8859-1" From: Marco Colombo Organization: ESI srl To: Francisco Reyes Subject: Re: Long running queries and timeouts Date: Mon, 21 Jan 2002 11:21:45 +0100 X-Mailer: KMail [version 1.3.1] Cc: pgsql-php@postgresql.org References: <20020120105039.V32376-100000@zoraida.natserv.net> In-Reply-To: <20020120105039.V32376-100000@zoraida.natserv.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archive-Number: 200201/33 X-Sequence-Number: 839 On Sunday 20 January 2002 16:56, Francisco Reyes wrote: > On Sat, 19 Jan 2002, Chadwick Rolfs wrote: > > On Sat, 19 Jan 2002, Francisco Reyes wrote: > > > New to the PHP/PostgreSQL combo. > > > I have a couple of queries which take a few minutes to run and we are > > > getting timeouts. Didn't find anything usefull on the archives. > > > > > > How are you handling long running queries on your PHP? [...] > After someone suggested I looked at "set_time_limit" I found that such > function doesn't account for DBconnection time. Afer reading that and your > suggestion to read httpd.conf I am starting to think that the likely place > of the timeout is the web server. > > Will play with the settings on httpd.conf > > I wonder how sites that display an update while the long query is running > do it. I have seen sites that display something like "retrieving info.. > please wait" and then right before the info comes up the waiting text > dissapears. Is that Javascript? Flash? I can't imagine how that could be > done with plain html. What timeout message do you get, exactly? I could be just the *client*, or the HTTP proxy, that times out if your script doesn't produce any output, and *not* the httpd process (thus, no need to look at httpd.conf). .TM.