Received: from mail.concept-factory.com (mail.concept-factory.com [204.181.16.156]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0K07XV05616 for ; Sat, 19 Jan 2002 19:07:34 -0500 (EST) (envelope-from mitch@doot.org) Received: from Mitch (cx2156713-a.phnx1.az.home.com [24.38.178.119]) by mail.concept-factory.com (Postfix) with SMTP id 5A64341FAD for ; Sat, 19 Jan 2002 17:07:15 -0700 (MST) Message-ID: <004601c1a146$d6a58940$0200000a@Mitch> From: "Mitch Vincent" To: References: Subject: Re: Long running queries and timeouts Date: Sat, 19 Jan 2002 17:10:15 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Archive-Number: 200201/24 X-Sequence-Number: 830 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