pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
upgrade issue
12+ messages / 7 participants
[nested] [flat]

* upgrade issue
@ 2002-08-16 14:35  Jodi Kanter <jkanter@virginia.edu>
  0 siblings, 2 replies; 12+ messages in thread

From: Jodi Kanter @ 2002-08-16 14:35 UTC (permalink / raw)
  To: pgsql-admin

Our system admin recently upgraded our Linux system from 7.1 to 7.3.
Apparently this upgrade also changed our postgres version from 7.1.3 to
7.2.1-5.

We are now getting the following error:

> An old version of the database format was found.
> You need to upgrade the data format before using PostgreSQL.
> See (Your System's documentation directory)/postgresql-7.2/README.rpm-dist
> for more information.

I have now read (all be it to late) the documentation warning of this
problem. Luckily we do not have any data that I need to save in the
database. I could easily get back to a functioning state if I could drop the
database and rebuild it via my schema.sql file. However, I cannot drop the
database unless I can get the postmaster started.
Can anyone advise?

Also, the upgrade doc that I am reading makes mention of a postgres-dump
command but there is no documentation on the system referencing this
command. Can someone please tell me more about it? Is it a new command?

Thanks so much for your assistance.
Jodi




^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2002-08-16 15:00  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Jodi Kanter <jkanter@virginia.edu>
  1 sibling, 0 replies; 12+ messages in thread

From: Tom Lane @ 2002-08-16 15:00 UTC (permalink / raw)
  To: Jodi Kanter <jkanter@virginia.edu>; +Cc: pgsql-admin

Jodi Kanter <jkanter@virginia.edu> writes:
> I have now read (all be it to late) the documentation warning of this
> problem. Luckily we do not have any data that I need to save in the
> database. I could easily get back to a functioning state if I could drop the
> database and rebuild it via my schema.sql file. However, I cannot drop the
> database unless I can get the postmaster started.

If you don't need any of the data then you can just rm -rf $PGDATA and
initdb.  (You might at least want to save the text configuration files
that appear in the top level $PGDATA directory, however, as consulting
them will make it easier to configure your new installation.)

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2002-08-16 18:04  Dmitry Morozovsky <marck@rinet.ru>
  parent: Jodi Kanter <jkanter@virginia.edu>
  1 sibling, 0 replies; 12+ messages in thread

From: Dmitry Morozovsky @ 2002-08-16 18:04 UTC (permalink / raw)
  To: Jodi Kanter <jkanter@virginia.edu>; +Cc: pgsql-admin

On Fri, 16 Aug 2002, Jodi Kanter wrote:

JK> Our system admin recently upgraded our Linux system from 7.1 to 7.3.
JK> Apparently this upgrade also changed our postgres version from 7.1.3 to
JK> 7.2.1-5.

[snip]

JK> problem. Luckily we do not have any data that I need to save in the
JK> database. I could easily get back to a functioning state if I could drop the
JK> database and rebuild it via my schema.sql file. However, I cannot drop the
JK> database unless I can get the postmaster started.
JK> Can anyone advise?

Well if you do not neet older database then just 'rm -rf $PGDATA' and then
do initdb. You'll got virgin empty database cluster.

Sincerely,
D.Marck                                   [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------




^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* upgrade issue
@ 2003-05-23 14:01  Jodi Kanter <jkanter@virginia.edu>
  0 siblings, 2 replies; 12+ messages in thread

From: Jodi Kanter @ 2003-05-23 14:01 UTC (permalink / raw)
  To: pgsql-admin

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

-- 

_______________________________
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
jkanter@virginia.edu <mailto:jkanter@virginia.edu>

 

 

 

^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2003-05-23 15:12  Oleg Bartunov <oleg@sai.msu.su>
  parent: Jodi Kanter <jkanter@virginia.edu>
  1 sibling, 1 reply; 12+ messages in thread

From: Oleg Bartunov @ 2003-05-23 15:12 UTC (permalink / raw)
  To: Jodi Kanter <jkanter@virginia.edu>; +Cc: pgsql-admin

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



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2003-05-23 15:47  Jodi Kanter <jkanter@virginia.edu>
  parent: Oleg Bartunov <oleg@sai.msu.su>
  0 siblings, 2 replies; 12+ messages in thread

From: Jodi Kanter @ 2003-05-23 15:47 UTC (permalink / raw)
  To: Oleg Bartunov <oleg@sai.msu.su>; +Cc: pgsql-admin

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>

 

 

 

^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2003-05-23 15:49  Joe Conway <mail@joeconway.com>
  parent: Jodi Kanter <jkanter@virginia.edu>
  1 sibling, 0 replies; 12+ messages in thread

From: Joe Conway @ 2003-05-23 15:49 UTC (permalink / raw)
  To: Jodi Kanter <jkanter@virginia.edu>; +Cc: pgsql-admin

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




^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2003-05-23 16:23  David F. Skoll <dfs@roaringpenguin.com>
  parent: Jodi Kanter <jkanter@virginia.edu>
  1 sibling, 1 reply; 12+ messages in thread

From: David F. Skoll @ 2003-05-23 16:23 UTC (permalink / raw)
  To: pgsql-admin

On Fri, 23 May 2003, Jodi Kanter wrote:

> 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.

I have a customer who symlinked libpg.so.3 to libpg.so.2 and he hasn't
reported problems.

I don't really advocate this, but at the same time, it's a quick fix :-)

--
David.



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2003-05-23 17:28  Joe Conway <mail@joeconway.com>
  parent: Jodi Kanter <jkanter@virginia.edu>
  1 sibling, 1 reply; 12+ messages in thread

From: Joe Conway @ 2003-05-23 17:28 UTC (permalink / raw)
  To: Jodi Kanter <jkanter@virginia.edu>; +Cc: Oleg Bartunov <oleg@sai.msu.su>; pgsql-admin

Jodi Kanter wrote:
> 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.

I just created a 7.3 RPM (based on DBD::pg 1.22 from
http://gborg.postgresql.org/project/dbdpg/download/download.php)

You can grab either the 7.3 binary RPM, or a source RPM from here:
   http://www.joeconway.com/

If you want to use the source RPM to build your own binary, do the 
following:

rpm -i perl-DBD-Pg-1.22-custom.1.src.rpm
rpm -ba --target i686 /usr/src/redhat/perl-DBD-Pg.spec
rpm -Uvh /usr/src/redhat/RPMS/i686/perl-DBD-Pg-1.22-custom.1.i686.rpm

HTH,

Joe





^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2003-05-23 17:49  Tom Lane <tgl@sss.pgh.pa.us>
  parent: David F. Skoll <dfs@roaringpenguin.com>
  0 siblings, 0 replies; 12+ messages in thread

From: Tom Lane @ 2003-05-23 17:49 UTC (permalink / raw)
  To: David F. Skoll <dfs@roaringpenguin.com>; +Cc: pgsql-admin

"David F. Skoll" <dfs@roaringpenguin.com> writes:
> I have a customer who symlinked libpg.so.3 to libpg.so.2 and he hasn't
> reported problems.
> I don't really advocate this, but at the same time, it's a quick fix :-)

The binary-level incompatibility only affects clients that use NOTIFY,
so for most applications you should be able to get away with the above.

The real solution of course is not to remove libpg.so.2 when you
upgrade, if you are not upgrading everything that uses it.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: upgrade issue
@ 2003-05-23 18:41  Jodi Kanter <jkanter@virginia.edu>
  parent: Joe Conway <mail@joeconway.com>
  0 siblings, 0 replies; 12+ messages in thread

From: Jodi Kanter @ 2003-05-23 18:41 UTC (permalink / raw)
  To: Joe Conway <mail@joeconway.com>; pgsql-admin

Thanks Joe and to all others that replied to our problem. Looks like we 
are up and running now!

Joe Conway wrote:

> Jodi Kanter wrote:
>
>> 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.
>
>
> I just created a 7.3 RPM (based on DBD::pg 1.22 from
> http://gborg.postgresql.org/project/dbdpg/download/download.php)
>
> You can grab either the 7.3 binary RPM, or a source RPM from here:
>   http://www.joeconway.com/
>
> If you want to use the source RPM to build your own binary, do the 
> following:
>
> rpm -i perl-DBD-Pg-1.22-custom.1.src.rpm
> rpm -ba --target i686 /usr/src/redhat/perl-DBD-Pg.spec
> rpm -Uvh /usr/src/redhat/RPMS/i686/perl-DBD-Pg-1.22-custom.1.i686.rpm
>
> HTH,
>
> Joe
>
>

-- 

_______________________________
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
jkanter@virginia.edu <mailto:jkanter@virginia.edu>

 

 

 

^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* upgrade issue
@ 2006-01-30 14:47  Josh O'Brien <obrien@zedxinc.com>
  0 siblings, 0 replies; 12+ messages in thread

From: Josh O'Brien @ 2006-01-30 14:47 UTC (permalink / raw)
  To: pgsql-admin

Hello all,

I am upgrading from postgresql v. 7.4 to 8.1.  I dump my database in 
plain text format and run the iconv command to fix the UTF8.  When i 
restore everything is populating but two tables.  I was wondering if 
anyone knows what would cause this.  Thanks in advance.

Josh O'Brien

Attachments:

obrien.vcf (text/x-vcard, 111B) download begin:vcard fn:Joshua O'Brien n:O'Brien;Joshua org:Zedx Inc. title:Database Administrator version:2.1 end:vcard
^ permalink raw reply [nested|flat] 12+ messages in thread


end of thread, other threads:[~2006-01-30 14:47 UTC | newest]

Thread overview: 12+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-08-16 14:35 upgrade issue Jodi Kanter <jkanter@virginia.edu>
2002-08-16 15:00 ` Tom Lane <tgl@sss.pgh.pa.us>
2002-08-16 18:04 ` Dmitry Morozovsky <marck@rinet.ru>
2003-05-23 14:01 upgrade issue Jodi Kanter <jkanter@virginia.edu>
2003-05-23 15:12 ` Oleg Bartunov <oleg@sai.msu.su>
2003-05-23 15:47   ` Jodi Kanter <jkanter@virginia.edu>
2003-05-23 16:23     ` David F. Skoll <dfs@roaringpenguin.com>
2003-05-23 17:49       ` Tom Lane <tgl@sss.pgh.pa.us>
2003-05-23 17:28     ` Joe Conway <mail@joeconway.com>
2003-05-23 18:41       ` Jodi Kanter <jkanter@virginia.edu>
2003-05-23 15:49 ` Joe Conway <mail@joeconway.com>
2006-01-30 14:47 upgrade issue Josh O'Brien <obrien@zedxinc.com>

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