From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | "S(dot) Balch" <sbalch(at)gmail(dot)com> |
Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: force JDBC driver fetch / autocommit parameters? |
Date: | 2011-10-21 23:48:04 |
Message-ID: | 4EA204B4.7060405@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/21/2011 10:38 PM, S. Balch wrote:
> Dave,
>
> We're just running the JVM out of memory with a large query result. By
> turning off autocommit and setting a reasonable fetch size this problem
> goes away. The application using this driver does have a way to set
> these, but it seems to be broken.
I don't think there's any support for forcing these params at the moment.
You could modify the JDBC driver to hard-code these parameters and just
use your hacked JDBC driver. That'd probably be a maintenance mess in
the long run, though. It'd be better to write a patch to add JDBC URL
parameter support for overriding them, start using a patched driver you
recompile yourself, and submit that to pgsql-jdbc(at)postgresql(dot)org for
inclusion in future versions so you don't have to worry about keeping it
up to date.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-10-22 00:41:44 | Re: adding a column takes FOREVER! |
Previous Message | Craig Ringer | 2011-10-21 23:45:11 | Re: postgres/postgis eats memory |