From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: wenjing <wjzeng2012@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org, tushar <tushar.ahuja@enterprisedb.com>
Subject: Re: [bug] Table not have typarray when created by single user mode
Date: Tue, 14 Apr 2020 14:00:19 -0400
Message-ID: <20200414180019.GA16161@alvherre.pgsql> (raw)
In-Reply-To: <9FCD07FF-CAF6-4220-8E07-E4E8037D6899@gmail.com>
On 2020-Apr-14, wenjing wrote:
> However, if such a table exists, an error with pg_upgrade is further raised
>
> ./initdb -k -D datanew
> ./pg_upgrade -d data -d datanew - b. -b.
>
> Restoring database schemas in the new cluster
> postgres
> *failure*
>
> Consult the last few lines of "pg_upgrade_dump_13580.log" for
> the probable cause of the failure.
> Failure, exiting
>
> pg_restore: from TOC entry 200; 1259 13581 TABLE t_create_by_standalone wenjing
> pg_restore: error: could not execute query: ERROR: pg_type array OID value not set when in binary upgrade mode
Maybe the solution is to drop the table before pg_upgrade.
(Perhaps in --check mode pg_upgrade could warn you about such
situations. But then, should it warn you specifically about random
other instances of catalog corruption?)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-bugs@postgresql.org
Cc: alvherre@2ndquadrant.com, wjzeng2012@gmail.com, tgl@sss.pgh.pa.us, tushar.ahuja@enterprisedb.com
Subject: Re: [bug] Table not have typarray when created by single user mode
In-Reply-To: <20200414180019.GA16161@alvherre.pgsql>
* 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