Funny, I'm trying to do the same thing. I think the problem is that V3
protocol (bind/execute) , Postgresql does not log the portal command
just the SQL statement. I'm busy trying to find the link in the archives
to this problem ..
On Fri, 2005-02-25 at 11:12, Alan Stange wrote:
> Hello all,
> I just noticed something and I thought I'd ask:
> When reading large chunks of data in the 7.4 JDBC client I would code
> something like this:
> st.executeQuery("select * from foo");
> which would result in queries to the postgresql server like this:
> DECLARE JDBC_CURS_588 CURSOR FOR select * from foo; fetch forward 1000
> from JDBC_CURS_588;
> with subsequent fetch forward queries being executed as the full result
> set is pulled in.
> In the 8.0 driver I don't see this happening. I see only the "select *
> from foo" query in the postgresql server log.
> Is the query result still being sent in batch chunks of 1000 rows, but
> using a different mechanism?
> -- Alan
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
CANdata Systems Ltd
In response to
pgsql-jdbc by date
|Next:||From: Markus Schaber||Date: 2005-02-25 18:08:45|
|Subject: Re: [JDBC] Where are we on stored procedures?|
|Previous:||From: Alan Stange||Date: 2005-02-25 16:12:38|
|Subject: setFetchSize question|