X-Original-To: pgsql-admin@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id 287EF925029 for ; Fri, 23 May 2003 12:01:41 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 83764-10 for ; Fri, 23 May 2003 12:01:26 -0400 (EDT) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by developer.postgresql.org (Postfix) with ESMTP id 1478B925110 for ; Fri, 23 May 2003 11:51:46 -0400 (EDT) Received: from [206.19.64.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 1763243; Fri, 23 May 2003 08:27:28 -0700 Message-ID: <3ECE431C.5000804@joeconway.com> Date: Fri, 23 May 2003 08:49:48 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jodi Kanter Cc: Postgres Admin List Subject: Re: upgrade issue References: <3ECE29A4.2010107@virginia.edu> In-Reply-To: <3ECE29A4.2010107@virginia.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/334 X-Sequence-Number: 8896 Jodi Kanter wrote: > We just upgraded one of our Red Hat 7.3 machines from postgresql version > 7.2.3 to version 7.3.2. All seemed to go smoothly until we received an > error via our web interface. The following error occurred: > > install_driver(Pg) failed: Can't load > '/usr/lib/perl5/site_perl/5.6.0/i386-linux/auto/DBD/Pg/Pg.so' for module > DBD::Pg: libpq.so.2: cannot open shared object file: No such file or > directory at /usr/lib/perl5/5.6.1/i386-linux/DynaLoader.pm line 206, > line 57. There was a libpq binary compatibility change between 7.2.x and 7.3.x, so libpq.so.2 was changed to libpq.so.3. I don't remember the specifics, and the archives don't seem searchable at the moment :-(. But in any case, I think you need to rebuild DBD::Pg against the newer libpq. > We solved the problem by moving libpq.so.2 from another machine. That > machine has not been upgraded yet and is still running postgresql > version 7.2.3. It would probably be better to create a libpq.so.2 symlink from libpq.so.3 until you can rebuild DBD::Pg. > I was hoping someone could give me some insight to why this occured. Did > we miss some part of the installation? I still have two machines to > upgrade and would like to avoid this on the others. The rpms all > appeared to have run without trouble. So, why didn't it install? The problem is the new libpq.so version. Not sure why RPM dependencies didn't warn you though. HTH, Joe