What I did was do the redhat install (was AS4) without checking postgres and the rpm installed fine. Asked for a redhat CD but no other issues. I believe you can uninstall it too, but I did not try that. Also make sure no security SELinux stuff. Joel Fradkin Wazagua, Inc. 2520 Trailmate Dr Sarasota, Florida 34243 Tel. 941-753-7111 ext 305 jfradkin@xxxxxxxxxxx www.wazagua.com Powered by Wazagua Providing you with the latest Web-based technology & advanced tools. C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc This email message is for the use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and delete and destroy all copies of the original message, including attachments. -----Original Message----- From: pgsql-admin-owner@xxxxxxxxxxxxxx [mailto:pgsql-admin-owner@xxxxxxxxxxxxxx] On Behalf Of Chris Hoover Sent: Wednesday, April 13, 2005 1:09 PM To: Joshua D. Drake Cc: PostgreSQL Admin Subject: Re: [ADMIN] Help installing 8.0.2 rpms on RH 3.0 Joshua D. Drake wrote: > >> Here is what I have: >> Virgin install of RH ES 3.0 from cd's (no update run right now) >> >> When I try to start installing the Postgresql rpms, I get the following: >> [root@localhost postgresql_rpms]# rpm -Uvh >> postgresql-libs-8.0.2-1PGDG.i686.rpm >> warning: postgresql-libs-8.0.2-1PGDG.i686.rpm: V3 DSA signature: >> NOKEY, key ID 748f7d0e >> error: Failed dependencies: >> libecpg.so.4 is needed by postgresql-libs-8.0.2-1PGDG >> libpgtypes.so.1 is needed by postgresql-libs-8.0.2-1PGDG >> libpq.so.3 is needed by postgresql-libs-8.0.2-1PGDG >> Suggested resolutions: >> rh-postgresql-libs-7.3.4-8.i386.rpm > > > It looks like you already have postgresql installed via RH 3. You need > to remove it first, then install 8. > > Honestly, when working with the RH ES version it is better to compile > anyway. > > Sincerely, > > Joshua D. Drake > > > > > I have checked, and postgresql is not installed on the system. Are there some dependent rpms that the postgresql-lib rpm needs? Why do you say it is better to compile (besides getting a "customized" postgresql)? Are there major problems with the rpm builds? Our management team really wants us to get away from compiling Postgresql if at all possible. So, I am going to need a very good argument to keep compiling Postgresql when we do this next project. Thanks, Chris ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
