On Fri, Sep 17, 2010 at 11:42 AM, Joshua J. Kugler <joshua@xxxxxxxxxxxxxx> wrote: > On Thursday 16 September 2010, Tom Lane elucidated thus: >> "Utsav Turray" <utsav.turray@xxxxxxxxxxxx> 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. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
