pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Jodi Kanter <jkanter@virginia.edu>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Postgres Admin List <pgsql-admin@postgresql.org>
Subject: Re: upgrade issue
Date: Fri, 23 May 2003 11:47:45 -0400
Message-ID: <3ECE42A1.8040805@virginia.edu> (raw)
References: <3ECE29A4.2010107@virginia.edu>
<Pine.GSO.4.55.0305231907220.28360@ra.sai.msu.su>
Recompiling Perl DBI is not a practical option. Did the developers
realize that a major version upgrade to libpq was going to break Perl
DBI/DBD-Pg?
Current versions of DBD-Pg use that libpg.so.2.
Oleg Bartunov wrote:
>Read this:
>
>http://fts.postgresql.org/db/msg.html?mid=1361754
>
>Oleg
>On Fri, 23 May 2003, 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.
>> at (eval 4) line 3
>>Compilation failed in require at (eval 4) line 3, <OR> line 57.
>>Perhaps a required shared library or dll isn't installed where expected
>> at sessionlib.pl line 1507
>>
>>The Pg driver is present, and was working before the upgrade. From this
>>error I understand that Pg.so can't load libpq.so.2. No surprise since
>>there is no /usr/lib/libpq.so.2 It appears that a symlink was created
>>to file that does not exist.
>>
>>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.
>>
>>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?
>>
>>Thanks
>>Jodi
>>
>>
>
> Regards,
> Oleg
>_____________________________________________________________
>Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
>Sternberg Astronomical Institute, Moscow University (Russia)
>Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
>phone: +007(095)939-16-83, +007(095)939-23-83
>
--
_______________________________
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
jkanter@virginia.edu <mailto:jkanter@virginia.edu>
view thread (12+ messages) latest in thread
Message-ID: <3ECE42A1.8040805@virginia.edu> Permalink: ../3ECE42A1.8040805@virginia.edu/ Also on: postgresql.org/message-id/3ECE42A1.8040805@virginia.edu ·
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: jkanter@virginia.edu, oleg@sai.msu.su Subject: Re: upgrade issue In-Reply-To: <3ECE42A1.8040805@virginia.edu> References: <3ECE29A4.2010107@virginia.edu> <Pine.GSO.4.55.0305231907220.28360@ra.sai.msu.su> <3ECE42A1.8040805@virginia.edu> * 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