From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Jaspreet Singh <jaspresingh(at)tesla(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: PG_UPGRADE FAILED FROM 9.5 to 11* |
Date: | 2020-06-18 20:19:10 |
Message-ID: | 20200618201910.GM7349@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Jun 18, 2020 at 06:42:11PM +0000, Jaspreet Singh wrote:
> Hi Team
>
> We are upgrading our 9.5 postgres database to 11* version and it failed with
> below error . please help .
>
>
>
> /usr/pgsql-11/bin/pg_upgrade -b /usr/pgsql-9.5/bin -B /usr/pgsql-11/bin -d /
> pgdata/data -D /var/lib/pgsql/11/data/
>
>
>
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
>
> pg_restore: [archiver (db)] Error from TOC entry 185; 1259 1183792 VIEW
> pg_stat_activity postgres
>
> pg_restore: [archiver (db)] could not execute query: ERROR: column
> pg_stat_activity.waiting does not exist
>
> LINE 27: "pg_stat_activity"."waiting",
>
> ^
>
> Command was:
You didn't show us the command that was causing the error. I am
thinking it might be a system view or function that references a renamed
system column. I suggest dropping the view/function in the old cluster,
running pg_upgrade, then recreating the view with the new column name.
Also, check the release notes for renamed columns.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Mattia Romagnoli | 2020-06-18 20:36:52 | Problems at columns |
Previous Message | PG Bug reporting form | 2020-06-18 19:24:08 | BUG #16502: EXPLAIN JSON format adds extra quotes around index names |