From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Jaspreet Singh <jaspresingh@tesla.com>
Cc: pgsql-bugs@postgresql.org <pgsql-bugs@postgresql.org>
Subject: Re: PG_UPGRADE FAILED FROM 9.5 to 11*
Date: Thu, 18 Jun 2020 17:15:47 -0400
Message-ID: <1596576.1592514947@sss.pgh.pa.us> (raw)
In-Reply-To: <20200618201910.GM7349@momjian.us>
References: <BYAPR16MB2789E8E00904B6ED17FE1955BE9B0@BYAPR16MB2789.namprd16.prod.outlook.com>
<20200618201910.GM7349@momjian.us>
Bruce Momjian <bruce@momjian.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, jaspresingh@tesla.com
Subject: Re: PG_UPGRADE FAILED FROM 9.5 to 11*
In-Reply-To: <1596576.1592514947@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox