pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: Upgrading O/S requires Postgres re-build?
Date: Thu, 09 Feb 2006 17:18:25 -0500
Message-ID: <60hd78fa6m.fsf@dba2.int.libertyrms.com> (raw)
References: <CB0FB369FF86E248A884BCC002562BCB010C0ACD@pisgsna01sxch01.ana.firstamdata.com>

htomeh@firstam.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? 



view thread (2+ messages)

Message-ID: <60hd78fa6m.fsf@dba2.int.libertyrms.com>
Permalink:  ../60hd78fa6m.fsf@dba2.int.libertyrms.com/
Also on:    postgresql.org/message-id/60hd78fa6m.fsf@dba2.int.libertyrms.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: Upgrading O/S requires Postgres re-build?
  In-Reply-To: <60hd78fa6m.fsf@dba2.int.libertyrms.com>
  References: <CB0FB369FF86E248A884BCC002562BCB010C0ACD@pisgsna01sxch01.ana.firstamdata.com> <60hd78fa6m.fsf@dba2.int.libertyrms.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox