pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David G. Johnston <david.g.johnston@gmail.com>
To: Murthy Nunna <mnunna@fnal.gov>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_upgrade failure upgrading from v10.8 to v14.4
Date: Fri, 22 Jul 2022 09:30:32 -0700
Message-ID: <CAKFQuwYKaU7eOpO2Z++TuDZX4GzVYmbgPpm0wdoRmW_O=FyGwQ@mail.gmail.com> (raw)
In-Reply-To: <DM8PR09MB667740FCD23BCFECA20E8A3CB8909@DM8PR09MB6677.namprd09.prod.outlook.com>
References: <DM8PR09MB667740FCD23BCFECA20E8A3CB8909@DM8PR09MB6677.namprd09.prod.outlook.com>

On Fri, Jul 22, 2022 at 9:19 AM Murthy Nunna <mnunna@fnal.gov> wrote:

>
> I encountered following error. Any help or insight is much appreciated.
>
>
> CREATE VIEW "public"."all_tables" AS
>
> SELECT ((("n"."nspname")::"text" || '.'::"text") ||
> ("c"."relname")::"text") AS "tablename",
>
>
>
You created a view that uses the catalogs and the structure of those
catalogs has changed.  pg_upgrade cannot fix this for you.  Unfortunately,
the only real solution is to have a pre-upgrade script that removes the not
unusable view, perform the upgrade, and then run a post-upgrade script that
replaces it with something that will work in the new system.  I'm unaware
of a version of PostgreSQL that would act as a transition version where
both versions of the view could exist, but you may wish to double-check
that if you think such a two-step upgrade path would be easier for you to
manage.

David J.

view thread (7+ messages)  latest in thread

Message-ID: <CAKFQuwYKaU7eOpO2Z++TuDZX4GzVYmbgPpm0wdoRmW_O=FyGwQ@mail.gmail.com>
Permalink:  ../CAKFQuwYKaU7eOpO2Z++TuDZX4GzVYmbgPpm0wdoRmW_O=FyGwQ@mail.gmail.com/
Also on:    postgresql.org/message-id/CAKFQuwYKaU7eOpO2Z++TuDZX4GzVYmbgPpm0wdoRmW_O=FyGwQ@mail.gmail.com

 · 

reply

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-admin@postgresql.org
  Cc: david.g.johnston@gmail.com, mnunna@fnal.gov
  Subject: Re: pg_upgrade failure upgrading from v10.8 to v14.4
  In-Reply-To: <CAKFQuwYKaU7eOpO2Z++TuDZX4GzVYmbgPpm0wdoRmW_O=FyGwQ@mail.gmail.com>

* 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