Received: from koza.acecape.com (koza2.acecape.com [66.9.36.222]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0N3pYl01228 for ; Tue, 22 Jan 2002 22:51:34 -0500 (EST) (envelope-from lists@natserv.com) Received: from p65-147.acedsl.com (p65-147.acedsl.com [66.114.65.147]) by koza.acecape.com (8.10.1/8.9.3) with ESMTP id g0N3pbK31534; Tue, 22 Jan 2002 22:51:37 -0500 (EST) Date: Tue, 22 Jan 2002 22:54:12 -0500 (EST) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: Josh Berkus cc: PostgresSQL PHP list Subject: Re: Long running queries and timeouts In-Reply-To: Message-ID: <20020122225323.D43699-100000@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200201/53 X-Sequence-Number: 859 On Tue, 22 Jan 2002, Josh Berkus wrote: > 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. So, no, we don't have > any sample code. In fact, we might be willing to buy some code that > creates a progress bar from someone who does have it ... I can't imagine a "progress bar". In particular if you are waiting for a reply from the DB server.