Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lhe1e-0002Rc-3G for pgsql-admin@arkaria.postgresql.org; Fri, 14 May 2021 20:03:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lhe1d-00085C-2d for pgsql-admin@arkaria.postgresql.org; Fri, 14 May 2021 20:03:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lhe1c-000854-QA for pgsql-admin@lists.postgresql.org; Fri, 14 May 2021 20:03:08 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lhe1a-0006WS-MX for pgsql-admin@lists.postgresql.org; Fri, 14 May 2021 20:03:07 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1lhe1Z-0006r6-J5; Fri, 14 May 2021 16:03:05 -0400 Date: Fri, 14 May 2021 16:03:05 -0400 From: Bruce Momjian To: Tim Cc: pgsql-admin@lists.postgresql.org Subject: Re: pg_upgrade not excluding system tables in EPAS Message-ID: <20210514200305.GA22341@momjian.us> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.