RE: PG_UPGRADE FAILED FROM 9.5 to 11*

From: Jaspreet Singh <jaspresingh(at)tesla(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>
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 21:56:30
Message-ID: BYAPR16MB27892E09EB34D54C6DF2B95CBE9B0@BYAPR16MB2789.namprd16.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks Tom
I have dropped the view and upgrade successful
Thanks for your quick response

-Jas

-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Thursday, June 18, 2020 2:16 PM
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Jaspreet Singh <jaspresingh(at)tesla(dot)com>; pgsql-bugs(at)postgresql(dot)org
Subject: Re: PG_UPGRADE FAILED FROM 9.5 to 11*

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Jun 18, 2020 at 06:42:11PM +0000, Jaspreet Singh wrote:
>> We are upgrading our 9.5 postgres database to 11* version and it
>> failed with below error . please help .
>>
>> pg_restore: [archiver (db)] Error while PROCESSING TOC:
>> pg_restore: [archiver (db)] Error from TOC entry 185; 1259 1183792
>> VIEW pg_stat_activity postgres
>> LINE 27: "pg_stat_activity"."waiting",

> 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.

Well, we can see that the problematic view is named "pg_stat_activity", but why would pg_dump have dumped a system view? I am thinking that the source database contains a duplicate (and now obsolete) copy of the pg_stat_activity view. Probably just getting rid of that would do the trick.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2020-06-19 00:00:15 Re: BUG #16501: Incorrect result. select multi_key_columns_range_partition_table
Previous Message Tom Lane 2020-06-18 21:50:16 Re: BUG #16503: excessive memory consumption.