In case anyone besides me is interested, installing these packages on CentOS4.2 seems to work. You can determine the correct mirror to use from: http://www.postgresql.org/ftp/binary/v8.0.4/linux/rpms/redhat/rhel- es-4/ The rpm command that I used was: rpm --upgrade --nodeps --hash -v <package url> Packages in order of installation: ftp://ftp3.ca.postgresql.org/pub/binary/v8.0.4/linux/rpms/redhat/rhe l-es-4/postgresql-libs-8.0.4-2PGDG.i686.rpm ftp://ftp3.ca.postgresql.org/pub/binary/v8.0.4/linux/rpms/redhat/rhe l-es-4/postgresql-contrib-8.0.4-2PGDG.i686.rpm ftp://ftp3.ca.postgresql.org/pub/binary/v8.0.4/linux/rpms/redhat/rhe l-es-4/postgresql-docs-8.0.4-2PGDG.i686.rpm ftp://ftp3.ca.postgresql.org/pub/binary/v8.0.4/linux/rpms/redhat/rhe l-es-4/postgresql-pl-8.0.4-2PGDG.i686.rpm ftp://ftp3.ca.postgresql.org/pub/binary/v8.0.4/linux/rpms/redhat/rhe l-es-4/postgresql-8.0.4-2PGDG.i686.rpm ftp://ftp3.ca.postgresql.org/pub/binary/v8.0.4/linux/rpms/redhat/rhe l-es-4/postgresql-server-8.0.4-2PGDG.i686.rpm ftp://ftp3.ca.postgresql.org/pub/binary/v8.0.4/linux/rpms/redhat/rhe l-es-4/postgresql-test-8.0.4-2PGDG.i686.rpm We are using 8.0.4 for development of a new application on a dedicated development server so stability and data conversion issues do not concern us for the moment. You are nonetheless advised not to install 8.0.4 over a 7.4.8 installation without first unloading all of the postgreSQL databases that you wish to preserve under 8.0.4. Regards, Jim -- *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3
Matt Arnilo S. Baluyos (Mailing Lists)
2005-Oct-25 20:31 UTC
[CentOS] PostgeSQL 8.0.4 on CentOS4.2
On 10/26/05, James B. Byrne <ByrneJB at harte-lyne.ca> wrote:> In case anyone besides me is interested, installing these packages > on CentOS4.2 seems to work. You can determine the correct mirror > to use from: > > http://www.postgresql.org/ftp/binary/v8.0.4/linux/rpms/redhat/rhel- > es-4/ > > The rpm command that I used was: > > rpm --upgrade --nodeps --hash -v <package url><snipped> Thanks Jim. Very useful guide - used it to upgrade our server to 8.0.4 (7.x.x would've been fine generally but I wanted the new ALTER COLUMN ... ALTER TABLE ... TYPE command). Seems --nodeps was the missing flag needed to install the packages without complaining about dependencies. -- Stand before it and there is no beginning. Follow it and there is no end. Stay with the ancient Tao, Move with the present.
James B. Byrne wrote:> In case anyone besides me is interested, installing these packages > on CentOS4.2 seems to work. You can determine the correct mirror > to use from: > > http://www.postgresql.org/ftp/binary/v8.0.4/linux/rpms/redhat/rhel- > es-4/ > > The rpm command that I used was: > > rpm --upgrade --nodeps --hash -v <package url> >errr... --nodeps ? what for ? - K
On Tue, 25 Oct 2005 15:11:56 -0600, Michael Best <mbest at pendragon.org> wrote:> 1. DON'T USE nodeps > > It's because the binaries don't have libpq.so.3 (if I remember > correctly). Installing it this way will just break those things > that need that library. > > Instead.... install the compat-postgresql-libsThat would have been really useful information to have, back on October 17 when I first asked the question about PostgreSQL 8 and CentOS 4 on this list. Lamar Owan provided a lot of help in his reply but I either missed any reference to the compatibility libraries or he failed to mention them. It is too bad that I was not aware of this when I carried out my procedure. However, as my recent post stated, this update was carried out on a dedicated development server. The each postgresql-8.0.4 package was first rpm -U --test installed with dependencies on to see what would break and determine if anything critical was in that list. The packages dependent upon libpq.so.3 on our server were: mod_auth_pgsql-2.0.1-6 dovecot-0.99.11-2.EL4.1 perl-DBD-Pg-1.31-6 postgresql-tcl-7.4.8-1.RHEL4.1 postgresql-python-7.4.8-1.RHEL4.1 Now the postgresql-*-7.4.8 stuff is not used on the development server, or anywhere else in our operation so far as we can determine. Those were deleted. Ditto for dovecot. Ditto for perl- DBD. Finally, the development machine does not provide httpd service so mod_auth_pgsql-2.0.1-6 is also redundant. Linux OS distributions are not religious dogma. Sometimes you just have to get something working and accept that fact that this choice will render less important things useless. This may not be the most elegant approach, but there is always a limit to the amount of time available to solve these kinds of problems. I appreciate that moving from postgres 7.x to 8.x is a far more involved issue for applications running against that dbms than simply loading the software. But all I needed was get a particular version of a particular package running on a tabula rasa server dedicated to development of a new application. The point being to avoid converting from pg 7.4 to 8.x in the future. At least all this information is now on the list for future reference. Regards, Jim -- *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3
Reasonably Related Threads
- RODBC : reading binary data from a TXT field belonging to a PostgeSQL table
- resolve errors with Samba 4 dns
- resolve errors with Samba 4 dns [RESOLVED]
- [PATCH 2/2] iommu/virtio: Add ops->flush_iotlb_all and enable deferred flush
- [PATCH 2/2] iommu/virtio: Add ops->flush_iotlb_all and enable deferred flush