BUG #14226: pg_upgrade for 8.4 to 9.4 failed
The following bug has been logged on the website:
Bug reference: 14226
Logged by: Tien Nguyen
Email address: nqtien310@gmail.com
PostgreSQL version: 9.4.0
Operating system: GNU/Linux
Description:
I did the cluster compatible check with "/usr/pgsql-9.4/bin/pg_upgrade -c -d
/var/lib/pgsql/data -D /var/lib/pgsql/9.4.test/data -b /usr/bin/ -B
/usr/pgsql-9.4/bin/", and it says "*Clusters are compatible*",
But then the process was failed when I run the actual upgrade
"/usr/pgsql-9.4/bin/pg_upgrade -d /var/lib/pgsql/data -D
/var/lib/pgsql/9.4.test/data -b /usr/bin/ -B /usr/pgsql-9.4/bin/
I consulted the log and saw these errors:
------------------
pg_restore: creating CONSTRAINT yodlee_user_accounts_pkey
pg_restore: creating INDEX concurrently
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2638; 1259 19738 INDEX
concurrently blueleaf
pg_restore: [archiver (db)] could not execute query: ERROR: CREATE INDEX
CONCURRENTLY cannot be executed from a function or multi-command string
Command was:
-- For binary upgrade, must preserve pg_class oids
SELECT
binary_upgrade.set_next_index_pg_class_oid('19738'::pg_catalog.oi...
------------------
I have no clue what these errors are about, please help .
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
nqtien310@gmail.com writes:
But then the process was failed when I run the actual upgrade
"/usr/pgsql-9.4/bin/pg_upgrade -d /var/lib/pgsql/data -D
/var/lib/pgsql/9.4.test/data -b /usr/bin/ -B /usr/pgsql-9.4/bin/
I consulted the log and saw these errors:
------------------
pg_restore: creating CONSTRAINT yodlee_user_accounts_pkey
pg_restore: creating INDEX concurrently
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2638; 1259 19738 INDEX
concurrently blueleaf
pg_restore: [archiver (db)] could not execute query: ERROR: CREATE INDEX
CONCURRENTLY cannot be executed from a function or multi-command string
Command was:
Drop or rename your index named "concurrently".
(PG 9.0 and up seem to quote that index name safely, but 8.4 doesn't,
and it's long out of support.)
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Mon, Jul 4, 2016 at 12:09:32PM -0400, Tom Lane wrote:
nqtien310@gmail.com writes:
But then the process was failed when I run the actual upgrade
"/usr/pgsql-9.4/bin/pg_upgrade -d /var/lib/pgsql/data -D
/var/lib/pgsql/9.4.test/data -b /usr/bin/ -B /usr/pgsql-9.4/bin/I consulted the log and saw these errors:
------------------
pg_restore: creating CONSTRAINT yodlee_user_accounts_pkey
pg_restore: creating INDEX concurrently
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2638; 1259 19738 INDEX
concurrently blueleaf
pg_restore: [archiver (db)] could not execute query: ERROR: CREATE INDEX
CONCURRENTLY cannot be executed from a function or multi-command string
Command was:Drop or rename your index named "concurrently".
(PG 9.0 and up seem to quote that index name safely, but 8.4 doesn't,
and it's long out of support.)
That is odd because pg_upgrade uses the _new_ 9.4 pg_dump to dump the
old cluster.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Bruce Momjian <bruce@momjian.us> writes:
On Mon, Jul 4, 2016 at 12:09:32PM -0400, Tom Lane wrote:
Drop or rename your index named "concurrently".
(PG 9.0 and up seem to quote that index name safely, but 8.4 doesn't,
and it's long out of support.)
That is odd because pg_upgrade uses the _new_ 9.4 pg_dump to dump the
old cluster.
Yeah, but pg_dump depends on the backend to do some of the work,
and 8.4 doesn't have quote-all-identifiers support.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Tue, Jul 26, 2016 at 09:52:37PM -0400, Tom Lane wrote:
Bruce Momjian <bruce@momjian.us> writes:
On Mon, Jul 4, 2016 at 12:09:32PM -0400, Tom Lane wrote:
Drop or rename your index named "concurrently".
(PG 9.0 and up seem to quote that index name safely, but 8.4 doesn't,
and it's long out of support.)That is odd because pg_upgrade uses the _new_ 9.4 pg_dump to dump the
old cluster.Yeah, but pg_dump depends on the backend to do some of the work,
and 8.4 doesn't have quote-all-identifiers support.
Ah, OK, makes sense.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs