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:
pgsql-bugs: please duplicate the upgrade-safety-check in the postgresql ebuild to ALSO exist in libpq, to help avoid this problem.
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*
Solved with dev-db/postgresql-{base,server}
