Re: trouble with pg_upgrade 9.0 -> 9.1

On Mon, Dec 17, 2012 at 03:33:40PM +0400, Groshev Andrey wrote:
> Hello!
> I'm trying to update a database from version 9.0 to 9.1 by pg_upgrade.
> The test is normal, but the actual conversion fails.
> This is a bug from pg_upgrade?
> I just saw this in the newsletter similar error with a note that it has been fixed in 9.1.2, but I already install 9.1.7.
>
> Restoring database schema to new cluster "/usr/pgsql-9.1/bin/psql" --set ON_ERROR_STOP=on --no-psqlrc --port 5432 --username "postgres" -f
> "/var/lib/pgsql/pg_upgrade/pg_upgrade_dump_db.sql" --dbname template1 >> "./log"
> psql:/var/lib/pgsql/pg_upgrade/pg_upgrade_dump_db.sql:153584: ПРЕДУПРЕЖДЕНИЕ: => как имя оператора считается устаревшим
> DETAIL: Это имя может быть вовсе запрещено в будущих версиях PostgreSQL.

The above is just a notice about =>, which is fine.

> Removing support functions from new cluster ok
> Removing support functions from new cluster ok
> "/usr/pgsql-9.1/bin/pg_ctl" -w -l "./log" -D "/var/lib/pgsql/9.1/data" stop >> "./log" 2>&1
> Restoring user relation files
>
> Mismatch of relation names: database "database", old rel public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel public.plob.ВерсияВнешнегоДокумент
> а$Документ
> Failure, exiting

I notice the first object is in the lob schema, but the second is lob
the the second is plob. That is a big dump (at least 153584 lines), so
is there anything unusual about this table? If you do a pg_dump
--schema-only on 'database' does the 'lob' table get dumped? There must
be something wrong, but I don't kno what.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +