From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Jaspreet Singh <jaspresingh(at)tesla(dot)com>, "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:15:47 |
Message-ID: | 1596576.1592514947@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2020-06-18 21:33:11 | BUG #16503: excessive memory consumption. |
Previous Message | Mattia Romagnoli | 2020-06-18 20:36:52 | Problems at columns |