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 1nmG0D-0003Sf-DC for pgsql-bugs@arkaria.postgresql.org; Wed, 04 May 2022 14:29:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nmG0C-0005jV-9Z for pgsql-bugs@arkaria.postgresql.org; Wed, 04 May 2022 14:29:16 +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 1nmEhG-0005Pu-Vy for pgsql-bugs@lists.postgresql.org; Wed, 04 May 2022 13:05:39 +0000 Received: from mail-ej1-x629.google.com ([2a00:1450:4864:20::629]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nmEhD-0003jk-JD for pgsql-bugs@lists.postgresql.org; Wed, 04 May 2022 13:05:37 +0000 Received: by mail-ej1-x629.google.com with SMTP id i27so2744998ejd.9 for ; Wed, 04 May 2022 06:05:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paymorrow-com.20210112.gappssmtp.com; s=20210112; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=Ouc4UK5Tfsifs61F90pDZoR/685s+oPAsUef9QKVZRo=; b=V40TRwjO/d5k1dMORiUybTZpOhhHD+p9y7eR3yT6X2fPTsEGfDjHUFy9ZznpzIMhbG G+xWJ+iYrxrJUp96yp9+ufUIALYo8wTcGpmYaYrltajB7g+rbz28KlaUxhKh2jXzx1HD on7IfLQRQnZvtQb3PO9q3P9nUlauwJAgrO19E1fJTcdH8bnIjWmBE2yMzMsTUGERRcsc 0swBVWuPVWvpbT4KlF1OfMUftqSYHFP2t6e+VvTXz85BPss7pe+cbFbL3DxwRxZRqSoB hJTFAISxCtQgX87UTrOPF2rj1acm4B7CWEUZ4axmwBfK5OY7JdmnOV3TwtwA8JDD3dYZ KPbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=Ouc4UK5Tfsifs61F90pDZoR/685s+oPAsUef9QKVZRo=; b=dEhiRakcvCcXBmYebbG1bcbQPDmsIR+Hr8uwSuRwXAYJgSIaYzq3qzviNKcWF3AhhT /u7JPEp4kPD1bJzzHqeIL6YYEZ4BqDIiaNavV8g+71JJtIbCQlHk+NW5ud71LHYZZ+8W YnC8DCJyy7qqBXORH2ehOav+9O/zNRStdQ2lFO6hXk15DCmYQHSEhdB46ipTcwDkVnTV N/jyLDvQan5L3J2xj2i08wfNUro6gLs8E8faR+J9dju+MZkfZdL67LQmdisE3/DoJwaL OPfLAdviQ5FbyCKc4yrJ67sBCuhT5ZgeiDTiqghP0q+kIYL0ZHRLZh/D1mIni791qY6Q 9IBQ== X-Gm-Message-State: AOAM532mGNzYqxDn6Db6Myhfe8zMthU0Nsk1a/LBaSdTljc2qDW0tTL1 XgwbBCfJa5X22BNY8s3zJylfuQsoTnyaHQ== X-Google-Smtp-Source: ABdhPJwAV5pnlRyn2ozTIXWyfeEXtk09jhT34R35WwBejdIyeXyH0cooIkyOo9k1lb9WP41+feJ6lw== X-Received: by 2002:a17:906:939a:b0:6f4:312e:b87e with SMTP id l26-20020a170906939a00b006f4312eb87emr16380487ejx.150.1651669533955; Wed, 04 May 2022 06:05:33 -0700 (PDT) Received: from vejsadalnx.localnet (kwall.cngroup.dk. [194.213.192.9]) by smtp.gmail.com with ESMTPSA id gx15-20020a1709068a4f00b006f3ef214e6esm5662317ejc.212.2022.05.04.06.05.32 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 May 2022 06:05:33 -0700 (PDT) From: Petr Vejsada To: pgsql-bugs@lists.postgresql.org Subject: pg_upgrade (12->14) fails on aggregate Date: Wed, 04 May 2022 15:05:32 +0200 Message-ID: <3383880.QJadu78ljV@vejsadalnx> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Team, we experienced pg_upgrade failing when attempted to upgrade from 12.10 to 14.2 (on AWS RDS) We had this aggregate: CREATE AGGREGATE public.array_accum(anyelement) ( SFUNC = array_append, STYPE = anyarray, INITCOND = '{}'); Syntax in version 14 is changed (we didn't try to run version 13) We solved it (in our case) dropping the aggregate before upgrade and re-create in using new syntax in V14: CREATE AGGREGATE public.array_accum(anycompatible) ( SFUNC = array_append, STYPE = anycompatiblearray, INITCOND = '{}'); but pg_upgrade shouldn't fail on this. I hope it can help to improve pg_upgrade process. Thanks. -- Best Petr