Hm, about memory exhausting I don't know, but the other day I tested the
limits of the text field in Postgres 6.5.(2 or 3). When ppl inserted text
in windows environment through html forms, then they got no more than
5000+a bit more symbols. Ok, I decided to test and inserted 8000+bit more
from linux and html form. What I got was corrupted table and no way to restore
data. And I am interested in parser or something too so I can see table
fields etc. to restore data if something so shitty happens. And yes I
didn't have backup, and yes it was important data :P Oh, about upgrading,
I don't maintain that machine, and half of its software should be upgraded
:P At least some little proggie to convert binary data to text would be of
some help in the future.
Just my idle thoughts though.
Greetings,Antti
On Wed, 25 Apr 2001, Mark Kirkwood wrote:
>
> Previously...
> >FATAL 1: Memory exhausted in AllocSetAlloc()
> >pqReadData() -- backend closed the channel unexpectedly.
> >This probably means the backend terminated abnormally
> >before or while processing the request.
> >
> >A table has been corrupted and i don't know why...
> >It's really hard to recover the table, and last time i lost some data ;-(
> >