| From: | Chandy G <vgchandru(at)yahoo(dot)com> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Shammat <shammat(at)gmx(dot)net> |
| Subject: | Re: postgres table statistics |
| Date: | 2024-06-13 07:11:53 |
| Message-ID: | 1777138388.3406832.1718262713257@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks Shammat! Seems to fit the bill, Will give it a try.
On Wednesday, 12 June, 2024 at 07:44:27 am GMT-7, Shammat <shammat(at)gmx(dot)net> wrote:
Chandy G schrieb am 12.06.2024 um 09:47:
> Eventhough pg jdbc driver provides a way to set fetch size to tune
> the driver to achieve better throughput, the JVM fails at the driver
> level when records of large size (say 200mb each) flows through.
> this forces to reduce the fetch size (if were to operate at a fixed
> Xmx setting of client jvm).
Did you try the driver's "adaptive fetch" feature?
https://jdbc.postgresql.org/documentation/use/#connection-parameters
| From | Date | Subject | |
|---|---|---|---|
| Next Message | yudhi s | 2024-06-13 07:43:06 | Re: Long running query causing XID limit breach |
| Previous Message | Chema | 2024-06-13 01:53:43 | Re: "permission denied to COPY to or from an external program" even with GRANT pg_execute_server_program |