From: | Christophe combet <chrisc_pro(at)yahoo(dot)fr> |
---|---|
To: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
Cc: | 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 14:19:43 |
Message-ID: | 1479303015.9175876.1595513983577@mail.yahoo.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Dear Dave,
The table definition is:
CREATE TABLE mytable ( column1 character varying(14) NOT NULL, column2 integer NOT NULL, column3 bytea NOT NULL);
ALTER TABLE ONLY mytable ADD CONSTRAINT mytable_pkey PRIMARY KEY (column1);
Column column3 contains zipped data (BLOB and toast table).
The full dump of the table (pg_dump as SQL text) is 24GB.
Thanks. Le jeudi 23 juillet 2020 à 15:24:54 UTC+2, Dave Cramer <davecramer(at)postgres(dot)rocks> a écrit :
On Thu, 23 Jul 2020 at 09:21, Christophe combet <chrisc_pro(at)yahoo(dot)fr> wrote:
autocommit=false & fetchSize=100 or 10000 : same exception.
42.2.10 still running.
Is there a very large column in there
Dave Cramerwww.postgres.rocks
Le jeudi 23 juillet 2020 à 14:30:56 UTC+2, Christophe combet <chrisc_pro(at)yahoo(dot)fr> a écrit :
Thank you for pointing the link between auto commit an buffering.
autocommit=false: same exception.
We try fetchSize.
Thanks. Le jeudi 23 juillet 2020 à 13:47:14 UTC+2, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> a écrit :
>can you try switching to autocommit=false?
+ you probably need to configure fetchSize as well.
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Solórzano | 2020-07-23 14:30:29 | Re: java.lang.OutOfMemoryError: GC overhead limit exceeded |
Previous Message | Vladimir Sitnikov | 2020-07-23 13:38:17 | Re: java.lang.OutOfMemoryError: GC overhead limit exceeded |