-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 18 May 2001 11:23, Hunter Hillegas wrote:
> I'm building a new server up and I usually build Postgres from source. I'm
> considering using the RPMs to make upgrades easier...
> Any disadvantage to using the RPMs that I might not be thinking of?
As long as you continue to perform the regular dump/reload cycle between
major version upgrades you should be fine.
Notice, though, that files are in different locations with the RPM -- this
may or may not disturb you, depending upon how much you enjoy micromanaging
your filesystem. See the README.rpm-dist that comes with the RPMset, or
visit the latest online version at a ftp.postgresql.org mirror nearest you in
the directory /pub/binary/v7.1.1/RPMS/
Most of the time the RPM upgrade is much simpler -- but, consider your
server's maintenance pattern and installed software base -- do you install
most software from RPM? Or do you install most software from source?
Installing via RPM is great if most everything else is installed via RPM --
as the RPM dependency database is full of all the necessary dependencies.
One definite advantage for many people of the RPMset is that you can install
its pieces to where you can have a minimal installation. Minimal for a
server would be postgresql-libs first, then postgresql and postgresql-server.
Then install whatever clients you may want or need. This takes less space
on disk than even a 'download whole tarball and configure and compile just
those pieces you want' installation.
One disadvantage is you have to wait on the sometimes slow RPM maintainer to
get a newer version uploaded. :-)
- --
Lamar Owen
WGCR Internet Radio
RPM Maintainer, PostgreSQL Global Development Group
1 Peter 4:11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7BUxv5kGGI8vV9eERAp5wAJ91951V65RqbHuFiTfoW0XsIspFbwCeL2rq
R3V79oYh9jFwqP4I2TkpS04=
=lSfP
-----END PGP SIGNATURE-----