From: Tom Lane <tgl@sss.pgh.pa.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 15:47:52 -0400
Message-ID: <2190580.1621021672@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKhLO5h9xVMkBFaexJKCiAo+Dd70VBmTRgeM8uNhsEU=rG-1zg@mail.gmail.com>
References: <CAKhLO5h9xVMkBFaexJKCiAo+Dd70VBmTRgeM8uNhsEU=rG-1zg@mail.gmail.com>
Tim <timfosho@gmail.com> writes:
> I am currently performing an upgrade of EPAS12 => EPAS13 via pg_upgrade...
You really ought to be discussing this with EDB Support, not here.
> It fails the check with this message:
> - Your installation contains system-defined composite type(s) in user
> tables.
Hmm. That is a new check in 13.3 ...
> 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.
... and I'm not sure what user_data is, but it's not present in community
Postgres. My guess as to what is happening here is that that pg_upgrade
test needs to be tweaked to understand which of the types that EPAS adds
are safe or not safe in this context. Anyway, you gotta talk to them.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, timfosho@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_upgrade not excluding system tables in EPAS
In-Reply-To: <2190580.1621021672@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