Re: missing chunk number 497 for toast value 504723663

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "Joshua J(dot) Kugler" <joshua(at)eeinternet(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: missing chunk number 497 for toast value 504723663
Date: 2010-09-17 19:27:07
Message-ID: AANLkTimfSzivEN2RCxCwxBJtvxBbpwp4smk2FoKY-z9p@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Sep 17, 2010 at 11:42 AM, Joshua J. Kugler
<joshua(at)eeinternet(dot)com> wrote:
> On Thursday 16 September 2010, Tom Lane elucidated thus:
>> "Utsav Turray" <utsav(dot)turray(at)newgen(dot)co(dot)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.
>
> 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 4.0. Presumably he
> is on a support contract, so moving to non-system software means he no
> longer has vendor support and upgrades for the packages installed on
> his system.  Pg 7.3.x is what came with RHEL 4.  Considering RHEL 3
> will EOL (finally) at the end of October, RH is going to be supporting
> Pg 7.3 for quite a while.  Hopefully they'll back port security fixes.

And 7.3.2 is the last update available for RHEL3? When I look at
centos 3 repos, they have 7.3.21 in them.
--
To understand recursion, one must first understand recursion.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message bricklen 2010-09-17 19:47:07 Re: PLPGSQL function to search function source for a list of terms
Previous Message Joshua J. Kugler 2010-09-17 17:42:42 Re: missing chunk number 497 for toast value 504723663