RE: PG_UPGRADE FAILED FROM 9.5 to 11*

Поиск
Список
Период
Сортировка
Искать
От
Jaspreet Singh
Тема
RE: PG_UPGRADE FAILED FROM 9.5 to 11*
Дата
Msg-id
BYAPR16MB27892E09EB34D54C6DF2B95CBE9B0@BYAPR16MB2789.namprd16.prod.outlook.com
Ответ на
Список
Дерево обсуждения
PG_UPGRADE FAILED FROM 9.5 to 11* Jaspreet Singh <jaspresingh@tesla.com>
Re: PG_UPGRADE FAILED FROM 9.5 to 11* Bruce Momjian <bruce@momjian.us>
Re: PG_UPGRADE FAILED FROM 9.5 to 11* Tom Lane <tgl@sss.pgh.pa.us>
RE: PG_UPGRADE FAILED FROM 9.5 to 11* Jaspreet Singh <jaspresingh@tesla.com>
Thanks Tom 
I have dropped the view and upgrade successful 
Thanks for your quick response 

-Jas

-----Original Message-----
From: Tom Lane  
Sent: Thursday, June 18, 2020 2:16 PM
To: Bruce Momjian 
Cc: Jaspreet Singh ; pgsql-bugs@postgresql.org
Subject: Re: PG_UPGRADE FAILED FROM 9.5 to 11*

Bruce Momjian  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



В списке pgsql-bugs по дате отправления
От: Tom Lane
Дата:
От: David Rowley
Дата:
FAQ