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 1kmiys-0003Ow-Qt for pgsql-admin@arkaria.postgresql.org; Tue, 08 Dec 2020 19:49:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kmiyr-0003VP-Lu for pgsql-admin@arkaria.postgresql.org; Tue, 08 Dec 2020 19:49:01 +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 1kmiyr-0003VI-Ep for pgsql-admin@lists.postgresql.org; Tue, 08 Dec 2020 19:49:01 +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 1kmiyl-0001wn-0l for pgsql-admin@lists.postgresql.org; Tue, 08 Dec 2020 19:49:00 +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 0B8Jmqu73264513; Tue, 8 Dec 2020 14:48:52 -0500 From: Tom Lane To: Scott Ribe cc: Pgsql-admin Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate In-reply-to: <074FE83A-E924-4787-9E68-27EB9CE142B3@elevated-dev.com> References: <074FE83A-E924-4787-9E68-27EB9CE142B3@elevated-dev.com> Comments: In-reply-to Scott Ribe message dated "Tue, 08 Dec 2020 11:55:33 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3264511.1607456932.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 08 Dec 2020 14:48:52 -0500 Message-ID: <3264512.1607456932@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Scott Ribe writes: > So I'm getting the error when migrating about not being able to GRANT SE= LECT on pg_catalog.pg_pltemplate, as referenced here: > https://www.postgresql-archive.org/pg-upgrade-issue-upgrading-10-gt-13-t= d6156401.html > Suggestions? There is probably an entry in pg_default_acl that is causing this. You could likely just manually remove that. regards, tom lane