Re: BUG #14221: using postgresql 9.1.22 to 9.3.13 failed using pg_upgrade

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: BUG #14221: using postgresql 9.1.22 to 9.3.13 failed using pg_upgrade
Дата
Msg-id 20160701145055.GA2588@momjian.us
обсуждение исходный текст
Ответ на BUG #14221: using postgresql 9.1.22 to 9.3.13 failed using pg_upgrade  (lishengxian123@163.com)
Список pgsql-bugs
On Fri, Jul  1, 2016 at 03:30:18AM +0000, lishengxian123@163.com wrote:
> pg_restore: creating VIEW pg_buffercache
> pg_restore: creating VIEW pg_stat_statements
> pg_restore: creating VIEW vw_currentqueries
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 167; 1259 103429584 VIEW
> vw_currentqueries dbadmin
> pg_restore: [archiver (db)] could not execute query: ERROR:  column
> pg_stat_activity.procpid does not exist
> LINE 14: SELECT "pg_stat_activity"."procpid", "pg_stat_activity"."cli...
>                 ^
>     Command was:
> -- For binary upgrade, must preserve pg_type oid
> SELECT binary_upgrade.set_next_pg_type_oid('103429586'::pg_catalog.oid);
>
> ==============
>
> As I know for the postgresql 9.3 the column already change to pid from
> procpid on table pg_stat_activity . please help to confirm if it bug or not
> . thanks a lot

Yeah, I suggest you drop the view, run pg_upgrade, then recreate the
view.

--
  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 по дате отправления:

Предыдущее
От: pange.akshaya@gmail.com
Дата:
Сообщение: BUG #14222: psqlODBC driver connection pooling not working for .net codebase
Следующее
От: scott@deltaex.com
Дата:
Сообщение: BUG #14223: stuck spinlock detected at bufmgr.c:1440