From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Christophe combet <chrisc_pro(at)yahoo(dot)fr> |
Cc: | Jorge Solórzano <jorsol(at)gmail(dot)com>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, pgsql-jdbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: java.lang.OutOfMemoryError: GC overhead limit exceeded |
Date: | 2020-07-23 15:57:16 |
Message-ID: | CADK3HHLcb8vFOwnTwdtE1SgkPH_ofZUaXNJrOvjE+_c2yL03nA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Thu, 23 Jul 2020 at 11:42, Christophe combet <chrisc_pro(at)yahoo(dot)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(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe combet | 2020-07-23 16:23:16 | Re: java.lang.OutOfMemoryError: GC overhead limit exceeded |
Previous Message | Christophe combet | 2020-07-23 15:53:44 | Re: java.lang.OutOfMemoryError: GC overhead limit exceeded |