Re: Upgrading O/S requires Postgres re-build?

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Upgrading O/S requires Postgres re-build?
Date: 2006-02-09 22:18:25
Message-ID: 60hd78fa6m.fsf@dba2.int.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

htomeh(at)firstam(dot)com ("Tomeh, Husam") writes:
> Server running Postgres 7.4.5 with:
>
> Red Hat Enterprise Linux AS release 3.90 (Nahant)
> Linux 2.6.9-1.648_ELsmp #1 SMP Tue Oct 26 12:24:18 EDT 2004 x86_64
> x86_64 x86_64 GNU/Linux
>
> I want to upgrade the O/S to:
>
> Red Hat Enterprise Linux AS release 4 (Nahant)
> Linux 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:29:47 EST 2005 x86_64 x86_64
> x86_64 GNU/Linux
>
>
> If I upgrade the O/S to the release stated above, do I need to
> re-install and build Postgres 7.4.5?

A kernel change shouldn't normally have any impact on whether
PostgreSQL would need to be recompiled or not.

If all of the libraries that PostgreSQL uses are binary compatible
between the two Linux *distribution* releases, then there oughtn't be
need to recompile PostgreSQL. And it is reasonably plausible that
that would be the case.

I'd expect the same PostgreSQL binaries to work; I actually found that
RHAT-compiled 32 bit binaries worked on SuSE running on AMD64, which
seemed quite remarkable.

But I'd be inclined to take a backup before the upgrade just in case
any surprises presented themselves...
--
let name="cbbrowne" and tld="cbbrowne.com" in String.concat "@" [name;tld];;
http://cbbrowne.com/info/nonrdbms.html
Why does sour cream have an expiration date?

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Dominik Składanowski 2006-02-09 22:58:37 Re: Postgresql 8.0 or 8.1 vs. latest Red Hat RPM
Previous Message Robert Perry 2006-02-09 21:21:52 Need query parameter in logs