From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | lishengxian123(at)163(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14221: using postgresql 9.1.22 to 9.3.13 failed using pg_upgrade |
Date: | 2016-07-01 14:50:55 |
Message-ID: | 20160701145055.GA2588@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jul 1, 2016 at 03:30:18AM +0000, lishengxian123(at)163(dot)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(at)momjian(dot)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 +
From | Date | Subject | |
---|---|---|---|
Next Message | scott | 2016-07-01 20:22:34 | BUG #14223: stuck spinlock detected at bufmgr.c:1440 |
Previous Message | Tom Lane | 2016-07-01 14:32:33 | Re: BUG #14220: pg_get_expr() with an incorrect relation id crashes the server |