pg_upgrade from 8.3.4 issue

From: Justin Arnold <jharnold81(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: pg_upgrade from 8.3.4 issue
Date: 2011-08-30 17:48:19
Message-ID: CAMr08oAKiDXYaYe4YQYEBH-fG_5aq82RiCA36EAsy3G_PSV53Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hey, I am trying to upgrade a CentOS 5.4 32bit test server running postgres
8.3.4 to postgres 9.1 RC1 and am running into an error I haven't seen
mentioned in the forums (at least dealing with the upgrade process). The
steps I ran through for the upgrade are...

>Stop postgres
>move /usr/local/pgsql to /usr/local/pgsql.8.3
>move /usr/pgdata/data to /usr/pgdata/data.8.3
>build 9.1 RC1 from source using "./configure --with-perl --with-openssl
--disable-integer-datetimes; make; make install"
>build and install pg_upgrade and pg_upgrade_support
>swap to postgres user
>run "/usr/local/pgsql/bin/initdb --lc-collate=C --lc-ctype=C
--lc-messages=C --lc-monetary=C --lc-numeric=C --lc-time=C -E SQL-ASCII -D
/usr/pgdata/data" to create the 9.1 cluster and set the settings to match
the old cluster
>/usr/local/pgsql/bin/pg_upgrade --link --old-datadir /usr/pgdata/data.8.3/
--new-datadir /usr/pgdata/data/ --old-bindir /usr/local/pgsql.8.3/bin/
--new-bindir /usr/local/pgsql/bin/

What I get is...
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 DB command
failed
SELECT * FROM pg_catalog.pg_prepared_xact()
ERROR: a column definition list is required for functions returning
"record"

Failure, exiting

The binaries for the 8.3.4 install were built from source using
the --with-perl --with-openssl options as well. Any thoughts on what I might
be able to do to fix or workaround this? Thanks!

- Justin

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Warasin 2011-08-30 17:48:28 Re: duplicate key violates unique on a nextval() field
Previous Message Daniel Verite 2011-08-30 17:43:35 Re: duplicate key violates unique on a nextval() field