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 1jOPrJ-0001q1-Mi for pgsql-bugs@arkaria.postgresql.org; Tue, 14 Apr 2020 18:00:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jOPrI-0002w0-FO for pgsql-bugs@arkaria.postgresql.org; Tue, 14 Apr 2020 18:00:28 +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 1jOPrI-0002vj-9J for pgsql-bugs@lists.postgresql.org; Tue, 14 Apr 2020 18:00:28 +0000 Received: from mail-qk1-x744.google.com ([2607:f8b0:4864:20::744]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jOPrF-0001kO-PP for pgsql-bugs@lists.postgresql.org; Tue, 14 Apr 2020 18:00:26 +0000 Received: by mail-qk1-x744.google.com with SMTP id c63so14317114qke.2 for ; Tue, 14 Apr 2020 11:00:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=r0C9dg6+m/W8VSXPSS7Q11lkDQ30UFImJ9Fg3buX2QI=; b=0K+9s6wvNVXI4mrHqL60KLefprZtQS5zcZnQHVlNdPJHnPaax2TUpZsEvTHktUA4fs IeMt52rLTs+3CpGx6ZWhrQluP8y+lncHnQGsfD/4xZOl+lqK8QiLP6x9VTb1KXT6X2Mw tL44jFeyWUIb7wmXRaPtAO+xCs67BmhsH07/+rSwHdCyp7azyc1Y1Tvpc4Q2T4odFLpt 04k8qfgrYe1iQe/Her8/rFWX2abJ+xIj4Ahpc2R8Q8PVQjv1BHE8xP0ZZYjYtuO0u2CZ wqOOH+Xr90keSxUPZHDwAxPeTd25tfBenpUN0GPKLAEyeatBNj1in2gRH9gN5Fo/FeoS e+WA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=r0C9dg6+m/W8VSXPSS7Q11lkDQ30UFImJ9Fg3buX2QI=; b=ZmlHM0SdHrPqDYfbsH47uOlP9R2qcZt+A2u2Ai5+EB/qUtJnFAy2BzgIlznWwuwIy0 z//rwv/8g9/+eGodmtHb53odFhBMkI/Uztit+UtyZKRY8qwOTZlKC7DqV0eVE1bsrAbH GWqbMiv5Qos2S3/SIiHrwWTw746CWsjLSe1hN70M6cDAD+NQ6zGiJd4rH4sQ33tGBi51 B5Mmh7k+OXwUJStSvINNPlVBsWZPj4KEv2HL/u8R/gnujQLWAjyLPkLVtWw+fv3MU7Je F0lL/SUYoBj9+tSM/1y/vf5BMAjHbuAIIOxwcDwt//jlabXaJombRpJLfWvb24J5KbyN hBzg== X-Gm-Message-State: AGi0PubOiK24tcAMKRsntVJq00Ai6RnFmvt2rJLtpi3uMalJSppRZGbi rDh3COZMgzPrrFuWQ3M3RluI6A== X-Google-Smtp-Source: APiQypKfbhfzz5u8KhVfC5KxhEnPPhVhAq/8znz5kRd0KlAuNArkvJFuEBs1hOKtvG9zKCQaSisXQA== X-Received: by 2002:a37:58c3:: with SMTP id m186mr23185412qkb.30.1586887223312; Tue, 14 Apr 2020 11:00:23 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id b13sm10454624qtp.46.2020.04.14.11.00.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Apr 2020 11:00:22 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 810AB300945; Tue, 14 Apr 2020 14:00:19 -0400 (-04) Date: Tue, 14 Apr 2020 14:00:19 -0400 From: Alvaro Herrera To: wenjing Cc: Tom Lane , pgsql-bugs@lists.postgresql.org, tushar Subject: Re: [bug] Table not have typarray when created by single user mode Message-ID: <20200414180019.GA16161@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9FCD07FF-CAF6-4220-8E07-E4E8037D6899@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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