Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: ResultSet & setFetchSize fails to stop heap failures
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: "U. George" <netbeans(at)gatworks(dot)com>
- Cc: pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: ResultSet & setFetchSize fails to stop heap failures
- Date: Wed, 28 May 2008 16:28:51 -0400 (EDT)
- Message-id: <Pine(dot)BSO(dot)4(dot)64(dot)0805281622000(dot)13145(at)leary(dot)csoft(dot)net>
On Wed, 28 May 2008, U. George wrote:
To do partial fetches you must turn autocommit off. See:Yup, that did it. I suppose there is a reason why no exception is thrown at the execute, or an error for the setFetchSize when autocommit is still on?
You can't throw an exception at setFetchSize because you could do setFetchSize(N) and then setAutoCommit(false). Throwing an exception at execute time is possible, but I don't think the driver should. Fetch size is just a hint, so it's not a failure if it isn't used.
Kris Jurka
- References:
- ResultSet & setFetchSize fails to stop heap failures
- From: U. George
- Re: ResultSet & setFetchSize fails to stop heap failures
- From: Kris Jurka
- Re: ResultSet & setFetchSize fails to stop heap failures
- From: U. George
- ResultSet & setFetchSize fails to stop heap failures
- Prev by Date: Re: ResultSet & setFetchSize fails to stop heap failures
- Next by Date: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
- Previous by thread: Re: ResultSet & setFetchSize fails to stop heap failures
- Next by thread: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
- Indexes: