Обсуждение: Table corrupted and data lost (second time in one month!!)
This is the second time in this month !!!! 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 ;-( Someone can help me to solve this problem ??? I don't want this table corrupted anymore .... The postgres version is 7.0.2 ... The aplication is CGI-Perl based, using DBI. The system is Mandrake 7.0, and the hardware a K6-2, 64Mb, 10Gb, etc... It runs without X. Thanks !! -- Fernando Moyano Frase del día: -------------- Este tagline es shareware. Envia 1000 pts para registrarlo. (*) SymeX ==> http://symex.lantik.com (*) WDBIL ==> http://wdbil.sourceforge.net (*) Informate sobre LINUX en http://www.linux.org
Fernando, > 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 > ;-( > > Someone can help me to solve this problem ??? I don't want this table > corrupted anymore .... My first thought would be hardware problems. Have you tried doing a full sector-by-sector scan on that HDD, or better yet, moving the whole database to an alternate server? BTW, I run Postgres on top of ReiserFS, which cuts down my disk errors significantly. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete informationtechnology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco
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 ;-( > I have never used 7.0.2 for any length of time....but I would recommend upgrading to 7.1 - many bugs have been fixed in this release - and hopefully not too many more introduced :) also adding more RAM would be a good idea, as 64Mb is not much these days ( I use apache 1.3.19 + mod perl 1.25 and regularly see 150Mb RSS when I run gtop ) This may be a Red Herring, but check to see you are not exhausing your swap space, as all sorts of odd errors can be encouraged by this... Cheers Mark
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 ;-( > >
"J.Fernando Moyano" <txinete@wanadoo.es> writes:
> The postgres version is 7.0.2 ...
I'd suggest an update to 7.1 ...
regards, tom lane