Well, I'm still at a guess what could cause the problem on the kind of
query I was executing (a "delete"). Kris' explanation with the deferred
trigger was the closest till now, except the trigger was not deferred,
and truncate still succeded with the "ON DELETE" trigger in place... so
I wonder now if there is some problem with the backend ? Maybe I should
post on the general list.
Cheers,
Csaba.
On Wed, 2005-07-13 at 14:07, Oliver Jowett wrote:
> 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
