| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> | 
|---|---|
| To: | "Josh Berkus" <josh(at)agliodbs(dot)com>, Francisco Reyes <lists(at)natserv(dot)com> | 
| Cc: | pgsql-php(at)postgresql(dot)org | 
| Subject: | Re: Long running queries and timeouts | 
| Date: | 2002-01-23 13:58:21 | 
| Message-ID: | 200201231358.g0NDwML18011@www1.translationforge | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-php | 
Le Mardi 22 Janvier 2002 16:52, Josh Berkus a écrit :
> Actually, my web developer and I talked about the programming necessary
>  to do this, and decided that it was easier to break up the
>  long-running function into 3 smaller functions.
Are you connecting from Netscape? I noticed long queries timeouted in 
Netscape. This is because Nescape waits for the entire content of a page 
before displaying it.
On the converse, when connecting from $M Internet Explorer, just echo a 
message like "Please wait during processing." and then "." everytime you run 
a query. IE refreshes content and there is no timeout.
Also, it is possible to set timeout time in /etc/php.ini. Set a high value 
like 600 seconds. Then you also need to allow more connections to PostgreSQL 
backend as described in this very interesting article : 
http://www.phpbuilder.com/columns/smith20010821.php3?page=2.
PostgreSQL can run very fast when well-optimized. You probably need to 
optimize the source code of queries themselves, probably writing some good 
PL/pgSQL server side code. If you need a GUI to do so, download and install 
Dave Page's excellent tool http://pgadmin.postgresql.org
Cheers,
Jean-Michel POURE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chadwick Rolfs | 2002-01-23 18:46:57 | Re: Not able to connect to server from PHP | 
| Previous Message | Jeff Self | 2002-01-23 13:57:11 | Re: Not able to connect to server from PHP |