Re: out of memory error on a delete command
От | Dave Cramer |
---|---|
Тема | Re: out of memory error on a delete command |
Дата | |
Msg-id | FD985253-E171-49FF-A443-913F28368BCF@fastcrypt.com обсуждение исходный текст |
Ответ на | Re: out of memory error on a delete command (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: out of memory error on a delete command
|
Список | pgsql-jdbc |
On 13-Jul-05, at 6:30 AM, Oliver Jowett wrote: > 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: Yes, this is what I meant. > > >>>> 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. > > -O > >
В списке pgsql-jdbc по дате отправления: