From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: out of memory error on a delete command |
Date: | 2005-07-13 10:30:17 |
Message-ID: | 42D4ED39.8060506@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Csaba Nagy wrote:
> OK, that might very well be a reason... is there a way to see what were
> the error messages ? Are they accumulating at server side or on the JDBC
> side ? If it's the JDBC side, is it reasonable maybe to just discard
> error messages if they are too many, or truncate if it's too big, in
> order to avoid this exception (which is not very helpful in itself...) ?
I think Dave actually means "too many warnings" (or NOTICEs?) which can
indeed fill Java heap as they're accumulated as SQLWarnings attached to
the relevant Statement. In that case, though, you'd see an
OutOfMemoryError. This exception:
>>>org.postgresql.util.PSQLException: ERROR: out of memory
is just the driver reporting a server-side error, so it's the server
that's run out of memory in this case.
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2005-07-13 11:24:40 | Re: patch to fix jdk 2 compile errors and v2 compatability |
Previous Message | Csaba Nagy | 2005-07-13 08:50:36 | Re: out of memory error on a delete command |