From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: out of memory error on a delete command |
Date: | 2005-07-13 12:07:19 |
Message-ID: | 42D503F7.6020008@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Dave Cramer wrote:
>>>>> 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.
>
>
> If this is the case, I wonder if we can be more verbose about the
> message. Seems we can't see the forest for the trees here.
Well, we're just propagating whatever the server tells us so if you want
a better message there it needs to be changed in the backend. We do
exactly the same for all backend errors, it's just that usually it's a
more obvious message along the lines of "ERROR: syntax error near ..."
or similar.
We could add some sort of "Error reported by backend:" prefix, I
suppose, but I'm not sure if that's really useful in most cases since
most errors are self-explanatory.
Kris has suggested adding more fields from the backend's error to the
default exception message, e.g. the DETAIL field. I'm not sure if that
would add anything in this particular case though.
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Csaba Nagy | 2005-07-13 12:14:07 | Re: out of memory error on a delete command |
Previous Message | Dave Cramer | 2005-07-13 11:26:17 | Re: out of memory error on a delete command |