Skip site navigation (1) Skip section navigation (2)

Re: Non-blocking SQL Execution

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Logan Bowers <logan(at)zillow(dot)com>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Non-blocking SQL Execution
Date: 2005-11-01 00:49:42
Message-ID: C0FA2AAC-0091-43DF-92AA-1AD5FF9105BD@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
It's probably easier to create a non-blocking thread which  
encapsulates the driver

And yes, the postgres driver blocks on the execute.

Dave
On 31-Oct-05, at 7:06 PM, Logan Bowers wrote:

> Hello,
>
>
>
> (sorry if this comes through twice)
>
>
>
> I'm running a web application that needs to run several queries  
> against several databases
>
> to satisfy a single request.  To minimize latency I'd like to be  
> able to issue
>
> "<PreparedStatement Object>.executeQuery()" on each connection,  
> allow the servers to
>
> execute the queries in parallel, and then only block when I attempt  
> to fetch the first
>
> row.
>
>
>
> My anecdotal experience with JDBC drivers in general are that they  
> block when you attempt
>
> to execute the query, not when you attempt to retrieve data.  Is  
> this the case for the
>
> Postgres driver?  Does anyone have a feel for how hard it would be  
> to modify the driver
>
> allow queries to be executed in the background?  Thanks!
>
>
>
> Logan Bowers
>
>
>
>

In response to

pgsql-jdbc by date

Next:From: Logan BowersDate: 2005-11-01 00:57:36
Subject: Re: Non-blocking SQL Execution
Previous:From: Logan BowersDate: 2005-11-01 00:06:45
Subject: Non-blocking SQL Execution

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group