pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Jodi Kanter <jkanter@virginia.edu>
Cc: Postgres Admin List <pgsql-admin@postgresql.org>
Subject: Re: upgrade issue
Date: Fri, 23 May 2003 08:49:48 -0700
Message-ID: <3ECE431C.5000804@joeconway.com> (raw)
In-Reply-To: <3ECE29A4.2010107@virginia.edu>
References: <3ECE29A4.2010107@virginia.edu>

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, 
> <OR> 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




view thread (12+ messages)  latest in thread

Message-ID: <3ECE431C.5000804@joeconway.com>
Permalink:  ../3ECE431C.5000804@joeconway.com/
Also on:    postgresql.org/message-id/3ECE431C.5000804@joeconway.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: mail@joeconway.com, jkanter@virginia.edu
  Subject: Re: upgrade issue
  In-Reply-To: <3ECE431C.5000804@joeconway.com>
  References: <3ECE29A4.2010107@virginia.edu> <3ECE431C.5000804@joeconway.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