[GENERAL] pg_upgrade 8.4 - 9.1 failures

2011-10-02 Thread Joseph S
I've tried the upgrade a few times, but I always get one type of failure
or another.

Performing Consistency Checks
-
Checking current, bin, and data directories ok
Checking cluster versions   ok
Checking database user is a superuser   ok
Checking for prepared transactions  ok
Checking for reg* system oid user data typesok
Checking for contrib/isn with bigint-passing mismatch   ok
Checking for large objects  warning

| Your installation contains large objects.
| The new database has an additional large object
| permission table.  After upgrading, you will be
| given a command to populate the pg_largeobject
| permission table with default permissions.

Creating catalog dump   ok

There were problems executing /usr/local/pgsql_84/bin/pg_ctl -w -l
/dev/null -D data84  stop  /dev/null 21
Failure, exiting

=

Performing Consistency Checks
-
Checking current, bin, and data directories ok
Checking cluster versions   ok
Checking database user is a superuser   ok
Checking for prepared transactions  ok
Checking for reg* system oid user data typesok
Checking for contrib/isn with bigint-passing mismatch   ok
Checking for large objects  warning

| Your installation contains large objects.
| The new database has an additional large object
| permission table.  After upgrading, you will be
| given a command to populate the pg_largeobject
| permission table with default permissions.

Creating catalog dump   ok
Checking for prepared transactions  ok
Checking for presence of required libraries ok

| If pg_upgrade fails after this point, you must
| re-initdb the new cluster before continuing.
| You will also need to remove the .old suffix
| from /home/postgres/data84/global/pg_control.old.

Performing Upgrade
--
Adding .old suffix to old global/pg_control   ok
Analyzing all rows in the new cluster   ok
Freezing all rows on the new clusterok
Deleting new commit clogs   ok
Copying old commit clogs to new server  ok
Setting next transaction id for new cluster ok
Resetting WAL archives  ok
Setting frozenxid counters in new cluster   ok
Creating databases in the new cluster   ok
Adding support functions to new cluster ok
Restoring database schema to new clusterok
Removing support functions from new cluster ok
Restoring user relation files

Mismatch of relation names: database dbname, old rel
pg_toast.pg_toast_1280475, new rel pg_toast.pg_toast_1202320
Failure, exiting

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Re: [GENERAL] pg_upgrade 8.4 - 9.1 failures

2011-10-02 Thread Peter Eisentraut
On sön, 2011-10-02 at 15:45 -0400, Joseph S wrote:
 Mismatch of relation names: database dbname, old rel
 pg_toast.pg_toast_1280475, new rel pg_toast.pg_toast_1202320
 Failure, exiting

This will be fixed in 9.1.2 (or get the code already from git).


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general