From: Bruce Momjian <bruce@momjian.us>
To: Tim <timfosho@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: pg_upgrade not excluding system tables in EPAS
Date: Fri, 14 May 2021 16:03:05 -0400
Message-ID: <20210514200305.GA22341@momjian.us> (raw)
In-Reply-To: <CAKhLO5h9xVMkBFaexJKCiAo+Dd70VBmTRgeM8uNhsEU=rG-1zg@mail.gmail.com>
References: <CAKhLO5h9xVMkBFaexJKCiAo+Dd70VBmTRgeM8uNhsEU=rG-1zg@mail.gmail.com>
On Fri, May 14, 2021 at 03:37:18PM -0400, Tim wrote:
> Hello Gentlemen,
>
> I am currently performing an upgrade of EPAS12 => EPAS13 via pg_upgrade...
> which I've done on a few clusters already with no issues, but this most recent
> run has me running into a problem.
>
> It fails the check with this message:
>
> • fatal
> • Your installation contains system-defined composite type(s) in user tables.
>
> And the output shows that it thinks sys.callback_queue_table.user_data is a
> user defined table. Which it is not, and cannot be dropped or altered. As I
> understand it should be excluding the sys schema that EPAS has. But for some
> reason it is not?
>
> I've checked all the system settings I can find, and can't figure why now it is
> having this issue. Am I missing something? Is there a way to define the system
> tables somewhere in postgres?
As far as community Postgres is concerned,
sys.callback_queue_table.user_data is not part of the community
distribution. You need to ask EDB about this.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
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: bruce@momjian.us, timfosho@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_upgrade not excluding system tables in EPAS
In-Reply-To: <20210514200305.GA22341@momjian.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