Re: java.lang.OutOfMemoryError: GC overhead limit exceeded
| От | Dave Cramer |
|---|---|
| Тема | Re: java.lang.OutOfMemoryError: GC overhead limit exceeded |
| Дата | |
| Msg-id | CADK3HHLcb8vFOwnTwdtE1SgkPH_ofZUaXNJrOvjE+_c2yL03nA@mail.gmail.com обсуждение исходный текст |
| Ответ на | java.lang.OutOfMemoryError: GC overhead limit exceeded (Christophe combet <chrisc_pro@yahoo.fr>) |
| Список | pgsql-jdbc |
On Thu, 23 Jul 2020 at 11:42, Christophe combet <chrisc_pro@yahoo.fr> wrote:
Dear Jorge,Thank you for the explanation and the pointer to the doc.Indeed, the autocommit=false + fetchSize combo is working. I did a mistake when trying the first time as suggested by Vladimir: I used createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY) which are not the good parameters to be used (bad copy/paste).With createStatement()+fetchSize+autocommit=false the exception disappeared.Thank you very much.Le jeudi 23 juillet 2020 à 16:31:06 UTC+2, Jorge Solórzano <jorsol@gmail.com> a écrit :The only change that could affect between 42.2.10 (which works based
on your first message), and 42.2.11+ is the introduction of the tuple
abstraction.
The autocommit=false + fetchSize combo should help with large tables:
https://jdbc.postgresql.org/documentation/head/query.html#fetchsize-example
Glad this works
Dave Cramer
www.postgres.rocks
В списке pgsql-jdbc по дате отправления: