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

Cursor returned from procedure ignores setFetchSize() on CallableStatement

From: "Brian G(dot) Huber" <brianghuber(at)yahoo(dot)com>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Cursor returned from procedure ignores setFetchSize() on CallableStatement
Date: 2004-06-08 15:16:01
Message-ID: 002301c44d6b$82b1b420$6400a8c0@bghthinkpad (view raw or flat)
Thread:
Lists: pgsql-jdbc
Hello all -

I need to return large result sets and therefore need a cursor with a small
fetch size (to avoid caching the entire query at once).  However, it appears
that when a cursor is returned from a callable statement setFetchSize is
ignored.

I set up a query that crashes with outofMemoryError if entire query is
cached.  I am able to sucsessfully use a Statement and setFetchSize() to
avoid the crash.  However, when I put the code in a procedure, the
outofMEmoryError throws before I even try to access the result set,
indicating that the entire query is caching.  This is true with or without
calling setFetchSize on the ResultSet in addition to the CallableStatement.

Is this a bug or am I doing something wrong?  Any comments greatly
appreciated. Thanks

Client
Code--------------------------------------------------------------------

cn.setAutoCommit(false);
CallableStatement proc = cn.prepareCall("{ ? = call reffunc2('cursor1') }");
proc.setFetchSize(100);
proc.registerOutParameter(1, Types.OTHER);
proc.execute();
rds = (ResultSet) proc.getObject(1);
rds.setFetchSize(100);
while (rds.next()){
...
}
Function--------------------------------------------------------------------

CREATE OR REPLACE FUNCTION public.reffunc2(refcursor) RETURNS refcursor AS '
BEGIN
OPEN $1 FOR SELECT ...<Large Query>...;
RETURN $1;
END;
' LANGUAGE 'plpgsql' VOLATILE

Responses

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2004-06-08 15:56:05
Subject: Re: Cursor returned from procedure ignores setFetchSize() on
Previous:From: Kris JurkaDate: 2004-06-07 21:38:01
Subject: Re: [PERFORM] Using a COPY...FROM through JDBC?

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