Re: BUG #15152: Java heap size - Mailing list pgsql-bugs

From Jaime Soler
Subject Re: BUG #15152: Java heap size
Date
Msg-id CAKVUGgQq8G=VLhpPVphuV9d=p81VF_2sEXzHqj2YqdxWnKkrLw@mail.gmail.com
Whole thread Raw
In response to BUG #15152: Java heap size  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15152: Java heap size
List pgsql-bugs
Hi,
If you have any question related to jdbc driver you should send it to pgsql-jdbc@postgresql.org . Also I would like to mention that you could use defaultRowFetchSize = int at connection level or setFetchSize at statement level to define how many record will be read by resultset  .

Regards


2018-04-13 8:50 GMT+02:00 PG Bug reporting form <noreply@postgresql.org>:
The following bug has been logged on the website:

Bug reference:      15152
Logged by:          Isaac  Arasavalli
Email address:      aistrong.hs@gmail.com
PostgreSQL version: 10.1
Operating system:   Windows 7
Description:       

When I fetch a table with huge data,  the result set fails with heap issue
with postgreSql.
But in DB2 it fetches group by group so it handles.
To fix there is an option to set autocommit off and set fetch size at
resultset.

For,  this I have to do lot of code change due to many occurrences of simila
issue in my huge application.

Is there any alternative to fix this,  like setting any parameters at data
source leve or any other way to minimize code change and solve.

Please help.


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15152: Java heap size
Next
From: PG Bug reporting form
Date:
Subject: BUG #15153: Serialize error (40001) on first statement suggestion