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

Re: statement caching proof of concept

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: till toenges <tt(at)kyon(dot)de>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: statement caching proof of concept
Date: 2006-06-19 23:59:20
Message-ID: 43EC5E93-607B-46C5-A133-00CE2E58F523@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Till,

Thanks, this is a great example. So how would any caching  
implementation deal with this?

I can think of copying the result set into the wrapper, but that  
could be prohibitively expensive.

Dave
On 19-Jun-06, at 7:56 PM, till toenges wrote:

> Dave Cramer wrote:
>> AFAIK Postgres doesn't allow concurrent statements on the same
>> connection, so I don't see how using multiple threads would work ?
>
> The statements wouldn't need to be concurrent in the sense of  
> happening
> at the same time:
>
> // stupid query
> String sql = "SELECT * FROM quicklychangingtable";
> PreparedStatement p1 = connection.prepareStatement(sql);
> PreparedStatement p2 = connection.prepareStatement(sql);
> ResultSet r1 = p1.executeQuery();
> // do something else for a while
> ResultSet r2 = p2.executeQuery();
>
> What happens with r1? Might be ok, but i'm not sure if this is  
> always true.
>
>
> Till
>


In response to

pgsql-jdbc by date

Next:From: till toengesDate: 2006-06-20 00:07:11
Subject: Re: statement caching proof of concept
Previous:From: till toengesDate: 2006-06-19 23:56:55
Subject: Re: statement caching proof of concept

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