From: | "Mitch Vincent" <mitch(at)doot(dot)org> |
---|---|
To: | <pgsql-php(at)postgresql(dot)org> |
Subject: | Re: Long running queries and timeouts |
Date: | 2002-01-20 00:10:15 |
Message-ID: | 004601c1a146$d6a58940$0200000a@Mitch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-php |
http://www.php.net/manual/en/function.set-time-limit.php will allow you to
set the timeout but you might post the queries and EXPLAIN output to
pg-general to see if there is something that can be done to speed them up...
Some well placed indexes always help!
> You can always use persistent connections. It's not a good idea to use
> too many, or you will be denied access to Postgres any other way, but it's
> a quick fix for the short run.
The maximum connections is a configuration parameter in postgresql.conf --
persistent connections are pretty cool but have been broken until recent
versions of PHP so I'm still hesitant using them..
> Long run and responsibility includes using an array, or an object to
> retrieve data.
Huh?
>You can always split queries up into many small queries.
What makes you say that?
-Mitch
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-01-20 00:32:55 | Re: "IS NOT NULL" != "NOT NULL" |
Previous Message | Tim Barnard | 2002-01-19 23:29:27 | Re: Clarification question |
From | Date | Subject | |
---|---|---|---|
Next Message | Cornelia Boenigk | 2002-01-20 02:59:42 | Re: Long running queries and timeouts |
Previous Message | Frank Bax | 2002-01-19 17:42:34 | Re: Long running queries and timeouts |