Re: java.lang.OutOfMemoryError: GC overhead limit exceeded

From: Christophe combet <chrisc_pro(at)yahoo(dot)fr>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
Cc: pgsql-jdbc(at)lists(dot)postgresql(dot)org
Subject: Re: java.lang.OutOfMemoryError: GC overhead limit exceeded
Date: 2020-07-23 11:06:41
Message-ID: 382025017.8991457.1595502401602@mail.yahoo.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dear Vladimir,
Thank you for your reply.
We forgot to mention the command line we used:   java -Duser.language=en -Duser.region=US -XX:ParallelGCThreads=1 -Xms8g -Xmx8g -jar our.jar jar_parameters
We generated a heap dump with 42.2.14  by adding  -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/mydump.hprof in the command line,  the dump file size is 9GB and contains not shareable data.
We are doing a "SELECT column1 FROM table1 ODER BY column1;" (column1 is   varchar(14) and the table contains 130,080,790 rows), when the exception occurs.
We tried 42.2.14 with the previous version of the database with 128,748,634 rows, the exception occurred to (it worked with 42.2.8). The exception is not linked to the increase in number of rows.
Yes, your are right, this a fetch of a very large resultset in a non-transactional manner (Autocommit:true).
Best.

Le jeudi 23 juillet 2020 à 11:28:25 UTC+2, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> a écrit :

Do you have a heap dump? Have you reviewed to identify the cause of the memory consumption?
Is it the case that you fetch a very large resultset in a non-transactional (autocommit=true) manner?
Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Vladimir Sitnikov 2020-07-23 11:25:14 Re: java.lang.OutOfMemoryError: GC overhead limit exceeded
Previous Message Vladimir Sitnikov 2020-07-23 09:28:06 Re: java.lang.OutOfMemoryError: GC overhead limit exceeded