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 1pXSXN-00014O-Re for pgsql-general@arkaria.postgresql.org; Wed, 01 Mar 2023 19:54:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pXSXM-0000eS-FF for pgsql-general@arkaria.postgresql.org; Wed, 01 Mar 2023 19:54:52 +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 1pXSXM-0000eJ-4o for pgsql-general@lists.postgresql.org; Wed, 01 Mar 2023 19:54:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pXSXF-0000IU-Ay for pgsql-general@postgresql.org; Wed, 01 Mar 2023 19:54:51 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 321JsUeU1547499; Wed, 1 Mar 2023 14:54:38 -0500 From: Tom Lane To: Arthur Ramsey cc: pgsql-general@postgresql.org Subject: Re: Failed upgrade from 12.11 to 14.4 In-reply-to: References: Comments: In-reply-to Arthur Ramsey message dated "Wed, 01 Mar 2023 10:32:23 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1547497.1677700470.1@sss.pgh.pa.us> Date: Wed, 01 Mar 2023 14:54:30 -0500 Message-ID: <1547498.1677700470@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Arthur Ramsey writes: > "Database instance is in a state that cannot be upgraded: pg_restore: from > TOC entry 1264; 1259 32392758 VIEW pg_stat_activity_allusers master > pg_restore: error: could not execute query: ERROR: column reference "query" > is ambiguous LINE 32: "get_sa"."query" > CREATE VIEW > "publiczugmgeaxkmwph5jgobvwmvzb9freg0s7"."pg_stat_activity_allusers" AS > SELECT "get_sa"."datid", "get_sa"."datname", "get_sa"."pid", > "get_sa"."usesysid", "get_sa"."usename", "get_sa"."application_name", > "get_sa"."client_addr", "get_sa"."client_hostname", "get_sa"."client_port", > "get_sa"."backend_start", "get_sa"."xact_start", "get_sa"."query_start", > "get_sa"."state_change", "get_sa"."wait_event_type", "get_sa"."wait_event", > "get_sa"."state", "get_sa"."backend_xid", "get_sa"."backend_xmin", > "get_sa"."query" FROM "publiczugmgeaxkmwph5jgobvwmvzb9freg0s7"."get_sa"() > "get_sa"("datid", "datname", "pid", "usesysid", "usename", > "application_name", "client_addr", "client_hostname", "client_port", > "backend_start", "xact_start", "query_start", "state_change", > "wait_event_type", "wait_event", "state", "backend_xid", "backend_xmin", > "query", "backend_type");". You're really expecting us to intuit a lot from this amount of detail, aren't you? But okay, I'll guess: I think this is a view on pg_stat_activity, and it's not accounting for the fact that pg_stat_activity gained some columns between v12 and v14. Probably your best bet is to drop that view, do the upgrade, and recreate the view with adjustments. regards, tom lane