From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | nqtien310(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed |
Date: | 2016-07-04 16:09:32 |
Message-ID: | 21758.1467648572@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
nqtien310(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-07-04 16:38:01 | Re: "insert [...] on conflict" hangs on conflict on an unmentioned gist index |
Previous Message | Tom Lane | 2016-07-04 15:00:33 | Re: "insert [...] on conflict" hangs on conflict on an unmentioned gist index |