Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed
От | Bruce Momjian |
---|---|
Тема | Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed |
Дата | |
Msg-id | 20160727002341.GE27321@momjian.us обсуждение исходный текст |
Ответ на | Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed
|
Список | 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 +
В списке pgsql-bugs по дате отправления: