Bug 177555

Summary:	Postgresql/libpg upgrade from 8.1.8 to libpg-8.2.4 and postgresql-8.2.4-r1 impossible
Product:	Gentoo Linux	Reporter:	Guido Flohr <guido>
Component:	New packages	Assignee:	PgSQL Bugs <pgsql-bugs>
Status:	RESOLVED FIXED
Severity:	major	CC:	esigra, gentoodoo, robbat2
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	183764

Description Guido Flohr 2007-05-07 21:02:05 UTC

The build of postgresql-8.2.4-r1 stops with a message saying that it cannot upgrade the existing database schemes from 8.1.8, and recommends using pg_dump to dump the old data first.  But pg_dump doesn't work any longer, because the dependency libpq has already been updated to 8.2.4.  It fails with:

pg_dump: error while loading shared libraries: libpq.so.4: cannot open shared object file: No such file or directory

Only fix for the user after the unsuccessful upgrade: Reemerge 8.1.8, dump the data with pg_dumpall, and then upgrade.

Reproducible: Always

Steps to Reproduce:

Comment 1 Robin Johnson archtester

2007-05-11 07:09:24 UTC

pgsql-bugs: please duplicate the upgrade-safety-check in the postgresql ebuild to ALSO exist in libpq, to help avoid this problem.

Comment 2 Michael Krelin 2007-06-16 11:32:26 UTC

Duplicate check makes sense for now, but generally, with new ebuilds it's unnecessary since all components from other slots can coexist peacefully. In this case, for example, I'd suggest first upgrading to slotted version of 8.1* and then to 8.2*

Comment 3 Tiziano Müller (RETIRED) gentoo-dev

2008-06-07 20:33:04 UTC

Solved with dev-db/postgresql-{base,server}