Received: from hapcibeno.freestart.hu (hapcibeno.freestart.hu [213.197.64.8]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f95Hubn80611 for ; Fri, 5 Oct 2001 13:56:38 -0400 (EDT) (envelope-from pgerzson@freestart.hu) Received: from erinyes.freestart.hu ([213.197.64.251]) by freestart.hu with esmtp (Freestart relay 2 (FS-Lin)) id 15pZQJ-0005m2-00 for ; Fri, 05 Oct 2001 20:10:11 +0200 Received: from line-74-236.dial.freestart.hu ([213.197.74.236] helo=jaguar) by erinyes.freestart.hu with smtp (Exim 3.32 #1 (Debian)) id 15pZKI-0003bs-00 for ; Fri, 05 Oct 2001 20:04:00 +0200 Message-ID: <019901c14dc7$2ad64280$01fdfea9@jaguar> From: "Papp Gyozo" To: References: <019d01c14dc4$7bdd1620$330a0a0a@rutgersinsurance.com> Subject: Re: Help with timeouts Date: Fri, 5 Oct 2001 19:57:00 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Scanner: exiscan by Freestart X-Archive-Number: 200110/38 X-Sequence-Number: 591 Yes, I'm also very curious now... Or can you post anything related to this error? ----- Original Message ----- From: "Adam Lang" To: Sent: Friday, October 05, 2001 7:38 PM Subject: Re: [PHP] Help with timeouts > Is it possible for us to go to the site and see the error message? > > Adam Lang > Systems Engineer > Rutgers Casualty Insurance Company > http://www.rutgersinsurance.com > ----- Original Message ----- > From: "Josh Berkus" > To: > Sent: Friday, October 05, 2001 12:55 PM > Subject: Re: [PHP] Help with timeouts > > > > Papp, > > > > > So is there anything you forgot to mention ;) > > > I mean everything works fine except this query or you couldn't test > > > the page > > > without the result. > > > > Nope. Just waitin' for the query. > > > > There's a couple of things that make us believe it's the browser: > > > > 1. The timeout message on Konqueror is a dialog box, not a web page. > > 2. Sometimes (we think) the query returns in just under 60 seconds (it's > > been clocked from the command line at 55) and it takes a few more > > seconds for the server to generate the HTML. The browser still times > > out. > > > > > Have you tried to optimize this query? > > > Maybe post to this list and wait for some suggestions... > > > > It's a procedure, actually, with about 16 steps. It's likely that we'll > > break it down into 3-4 sub procedures for "progress reporting" purposes. > > This will slow down the process overall but prevent browser timeouts. > > > > -Josh > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html