| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | aistrong(dot)hs(at)gmail(dot)com |
| Subject: | BUG #15152: Java heap size |
| Date: | 2018-04-13 06:50:34 |
| Message-ID: | 152360223433.31227.17170769780949067555@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15152
Logged by: Isaac Arasavalli
Email address: aistrong(dot)hs(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Soler | 2018-04-13 07:27:57 | Re: BUG #15152: Java heap size |
| Previous Message | Michael Paquier | 2018-04-13 01:10:46 | Re: BUG #15151: Error with wal replay after planned manual switchover. |