pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adam Lang <aalang@rutgersinsurance.com>
To: pgsql-php@postgresql.org
Subject: Re: Help with timeouts
Date: Fri, 5 Oct 2001 12:01:13 -0400
Message-ID: <010a01c14db6$f57a3ca0$330a0a0a@rutgersinsurance.com> (raw)
References: <web-142387@davinci.ethosmedia.com>

Ooops!

I realise I sent my original answer to a wrong list.  Sorry.
----------------------------------------------------------------------------
-
Look at the script timeout settings in php.ini... not the httpd.conf.

Send the $50 a breast cancer charity... or me.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Josh Berkus" <josh@agliodbs.com>
To: <pgsql-php@postgresql.org>
Sent: Friday, October 05, 2001 11:26 AM
Subject: Re: [PHP] Help with timeouts


> Folks,
>
> Some answers:
>
> > I have a very complex database operation that can sometimes take
> > 70-90
> > seconds to return results. The web page which displays the results,
> > however, seems to always timeout at 60seconds despite setting the
> > Apache
> > timeout to 300 seconds and set_time_limit to 240.
>
> After a helpful web guru called us up from our post, we were able to
> diagnose what's happening here (donation to be announced later):
>
> Regardless of the Timeout and set_time_limit() settings, most browsers
> will time out at 60 seconds.
>
> This is obviously a huge annoyance. Therefore I am offering a *second*
> charity prize to any person who can give me code (PHP or Perl) which
> will display a "Processing" screen with an auto-reload to keep the
> browser interested while waiting 60 to 120 seconds for a database
> response in the background. *Someone* must have done this already, even
> though multi-threading in PHP & Perl is nigh impossible.
>
> -Josh Berkus
>


----------------------------------------------------------------------------
----


>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>






view thread (17+ messages)  latest in thread

Message-ID: <010a01c14db6$f57a3ca0$330a0a0a@rutgersinsurance.com>
Permalink:  ../010a01c14db6$f57a3ca0$330a0a0a@rutgersinsurance.com/
Also on:    postgresql.org/message-id/010a01c14db6$f57a3ca0$330a0a0a@rutgersinsurance.com

 · 

reply

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: aalang@rutgersinsurance.com
  Subject: Re: Help with timeouts
  In-Reply-To: <010a01c14db6$f57a3ca0$330a0a0a@rutgersinsurance.com>
  References: <web-142387@davinci.ethosmedia.com> <010a01c14db6$f57a3ca0$330a0a0a@rutgersinsurance.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