Re: [GENERAL] missing chunk number 497 for toast value 504723663

2010-09-17 Thread Joshua J. Kugler
On Thursday 16 September 2010, Tom Lane elucidated thus: Utsav Turray utsav.tur...@newgen.co.in writes: I am using postgres 7.3.2 on RHEL 4.0. Egad. Secondly what are probable reasons behind corruption and what can we do to prevent this error. Update. Whatever reasons you might

Re: [GENERAL] missing chunk number 497 for toast value 504723663

2010-09-17 Thread Scott Marlowe
On Fri, Sep 17, 2010 at 11:42 AM, Joshua J. Kugler jos...@eeinternet.com wrote: On Thursday 16 September 2010, Tom Lane elucidated thus: Utsav Turray utsav.tur...@newgen.co.in writes: I am using postgres  7.3.2  on RHEL 4.0. Egad. Secondly what are probable  reasons behind corruption and

Re: [GENERAL] missing chunk number 497 for toast value 504723663

2010-09-17 Thread Tom Lane
Joshua J. Kugler jos...@eeinternet.com writes: On Thursday 16 September 2010, Tom Lane elucidated thus: Update. Whatever reasons you might have for running 7.3.2 are bad ones. Disclaimer: I agree with Tom; running 7.3.2 is a bad idea. That said: like he said, he can't. He's running RHEL

Re: [GENERAL] missing chunk number 497 for toast value 504723663

2010-09-17 Thread Joshua J. Kugler
On Friday 17 September 2010, Tom Lane elucidated thus: Joshua J. Kugler jos...@eeinternet.com writes: On Thursday 16 September 2010, Tom Lane elucidated thus: Update. Whatever reasons you might have for running 7.3.2 are bad ones. Disclaimer: I agree with Tom; running 7.3.2 is a bad

[GENERAL] missing chunk number 497 for toast value 504723663

2010-09-16 Thread Utsav Turray
Dear All , I am using postgres 7.3.2 on RHEL 4.0. I know the version is too old but I have no option upgrading the postgres version. I have a table with a column type text. The column consists large data ranging from 500 kb to 900 kb. Total there are 5 records approximately.

Re: [GENERAL] missing chunk number 497 for toast value 504723663

2010-09-16 Thread Tom Lane
Utsav Turray utsav.tur...@newgen.co.in writes: I am using postgres 7.3.2 on RHEL 4.0. Egad. Secondly what are probable reasons behind corruption and what can we do to prevent this error. Update. Whatever reasons you might have for running 7.3.2 are bad ones.