pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guy Smith <guy.smith@db.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Concerned about previous version still in place
Date: Thu, 19 Feb 2004 10:52:16 +0000
Message-ID: <OF39CC7F63.2A5441D5-ON80256E3F.003912D3@db.com> (raw)

Hi,

Some time ago I upgraded to 7.3.4 from 7.2.2 and am now looking to upgrade again to 7.4.1.

At the time I upgraded to 7.3.4 I took a very cautious approach and ran make install after a configure --prefix /home/postgres/root (and created a new database similarly) so that I could easily run up 7.2.2 installed under /usr/bin (originally installed there by rpm) if I needed to fail back.  I'm now looking to install 7.3.4 "officially" as a precursor to beta installing 7.4.1 and have rerun configure without the --prefix and performed a make install.  This has installed to /usr/local/pgsql/bin et al as would be expected from reading INSTALL (which, of course, I've done after the event!).  My concern is that I now have 7.2.2 executables installed at /usr/bin and libraries in /usr/lib and so on, which may be used by my site code inadvertently.

I believe I could configure --prefix /usr and make install again to overwrite these but I've also noticed that there are additional files in /usr/include/pgsql that don't exist in /usr/local/pgsql/include so am concerned I could create a mess.  I would also like to move towards a consistent approach where my team don't need to consider --prefix for the final install, we go with the default.

I'm running SuSE Linux 8.2 - can I just use rpm to remove postgresql-7.2.2-90.i586.rpm without breaking anything?

Thanks,
Guy

----------------------------------------------------------------------------
Project Manager - SourceForge
Deutsche Bank [/]
----------------------------------------------------------------------------




--

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.





Message-ID: <OF39CC7F63.2A5441D5-ON80256E3F.003912D3@db.com>
Permalink:  ../OF39CC7F63.2A5441D5-ON80256E3F.003912D3@db.com/
Also on:    postgresql.org/message-id/OF39CC7F63.2A5441D5-ON80256E3F.003912D3@db.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: guy.smith@db.com
  Subject: Re: Concerned about previous version still in place
  In-Reply-To: <OF39CC7F63.2A5441D5-ON80256E3F.003912D3@db.com>
  References: <OF39CC7F63.2A5441D5-ON80256E3F.003912D3@db.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