The following bug has been logged on the website:
Bug reference: 6733
Logged by: Mike Wilson
Email address: mfwilson@gmail.com
PostgreSQL version: 9.1.4
Operating system: Solaris 10
Description:=20=20=20=20=20=20=20=20
Filing this under PG914 since there isn't an option for PG9.2beta2.=20
Possibly this should be filed elsewhere? If so apologies in advance.
We are starting to prepare for the PG9.2 release so I have been performing
some test pg_upgrades on our existing PG8.4.2 cluster. We have a sizable
database and limited space so we have been testing upgrading our cluster
using --link mode of pg_upgrade. After performing an upgrade though the new
PG92 database has only empty tables.
Running this:
export NEWPG=3D/usr/postgres/postgresql-9.2.0_slony-2.1.1
export OLDPG=3D/usr/postgres/pg842_slony210
LD_LIBRARY_PATH=3D${NEWPG}/lib PATH=3D${NEWPG}/bin:${PATH} /usr/bin/time
${NEWPG}/bin/pg_upgrade --verbose --link \
--old-datadir=3D/opt/postgres/db/root/old
--new-datadir=3D/opt/postgres/db/root/new --old-bindir=3D${OLDPG}/bin/64/ \
--new-bindir=3D${NEWPG}/bin/ --old-port=3D5432 --new-port=3D5920 --user=3Dp=
ostgres
This runs without errors and I am able to start the new upgraded PG92beta2
cluster. The schemas appear to be correct as well as the table definitions
and other schema objects. The tables themselves though are all empty. Not
sure what is going on