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 1opl09-0002Ot-3H for pgsql-admin@arkaria.postgresql.org; Tue, 01 Nov 2022 06:43:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1opl07-0002Ep-Vp for pgsql-admin@arkaria.postgresql.org; Tue, 01 Nov 2022 06:43:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1opl07-0002Eg-Ko for pgsql-admin@lists.postgresql.org; Tue, 01 Nov 2022 06:43:55 +0000 Received: from mail-wr1-x433.google.com ([2a00:1450:4864:20::433]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1opl05-0000yz-8X for pgsql-admin@postgresql.org; Tue, 01 Nov 2022 06:43:55 +0000 Received: by mail-wr1-x433.google.com with SMTP id w14so18838318wru.8 for ; Mon, 31 Oct 2022 23:43:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=oJYSyj2KO9HThW5xQ/34uGjsajBHJjb8aL9AJ3NzG/A=; b=rOIocES3rYmZDjmAVVaiew59SbAm0Zkvp526DoaQI/GWp4IM/JI3tpjHSHTDfK+s+I VLVKJHcpYt+snrOh2J8ySoA/q2aM7s1Mi/zhf0TI4+vq/o0SRPrn+Kh34gBZK4C/O1ea ik+furSsTAbBCAZIpwRq35UXz8mOA4ZUpB6rK6I8XJQnpR+8UlBaBwHmIrCuODLcOSOy xc3oL0DUJFIrN1xUr+mKiyiXehwmU2shVv/BnpWYGIW9AA6YAihKZGiWLqC5qQ8NtYZc ICGieVEJn8wOZk+frFiaOsApJIC1ok8BuhrTneJXEKkASOtT9r259JJFGhzVGbpHBV8a 3yqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=oJYSyj2KO9HThW5xQ/34uGjsajBHJjb8aL9AJ3NzG/A=; b=vVbL24aqCiY4Upyo+LPO8u7Nh41JmtYBnlwF9Tf7hVSaEAonUUiVAK8CjAsCSOrQkC 8wIQ/SiNHovwk4qyqvqZYwLPbyU7aA8NNUvLUKeKu7Sd+G+PGqfc/3qRIGEnWfDzWL+6 ZsJ56P/TMI9iRhnrEp9z4QGIG+N4PEdzQG+15JSUeny5OhJmcy/kc7957sS6rCYwmJ1x KfSCcYNRewtXc9QSpKGkbPo6qSaqYGk4L8PlbHxUeZ1RWu/QIbqcvTOdkMWyJlxw4jdb tytMwYGB0RabrWO38W1dW6aLfvAx8qGFz0CRz5vN2dy9P7E8V5ia50V2DxMZNzmfraRS 8YAA== X-Gm-Message-State: ACrzQf3txqCqpeqwGuLODUvWoDedJ50JUVWlu7yM5cvulatGwSjuAXtb Pi1LGy8559es8ZOivvFzC9fh6w== X-Google-Smtp-Source: AMsMyM5BROv911tYgCkOXBgUW8GlIk2FUqnjL953fYr+eLBj6nJDtUzPMbsWsMALypFBCk4EkREVcw== X-Received: by 2002:a05:6000:170d:b0:236:6aa1:8a56 with SMTP id n13-20020a056000170d00b002366aa18a56mr10409059wrc.302.1667285032322; Mon, 31 Oct 2022 23:43:52 -0700 (PDT) Received: from localhost.localdomain (178-190-182-20.adsl.highway.telekom.at. [178.190.182.20]) by smtp.gmail.com with ESMTPSA id be7-20020a05600c1e8700b003a83ca67f73sm9880031wmb.3.2022.10.31.23.43.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 31 Oct 2022 23:43:52 -0700 (PDT) Message-ID: <269666903b69c2b9548fe75826174c14e103b818.camel@cybertec.at> Subject: Re: Pg_upgrade issue From: Laurenz Albe To: abbas alizadeh , pgsql-admin Date: Tue, 01 Nov 2022 07:43:51 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2022-11-01 at 07:53 +0400, abbas alizadeh wrote: > I tried to upgrade one of my databases from v11 to v14. > But I faced following error during upgrade: > “System catalog modifications are currently disallowed” > This is regarding to postgis extention that is installed in pg_catalog, apparently I can’t move extention from pg_catalog to public schema. > In the other hand I can’t drop postgis extention as it uses frequently in different tables. > Is there any option like “allow_system_table_mods” for pu_upgrade? > Any idea how can I sort this issue? Perhaps you can pre.install the extension is a proper schema on v14, then dump and restore and ignore the error from CREATE EXTENSION. Other than that, you would be reduced to fixing the old installation, which would entail catalog modifications that might break your database. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com