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 1kn37f-0008A4-Tp for pgsql-admin@arkaria.postgresql.org; Wed, 09 Dec 2020 17:19:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kn37e-0005Kh-RA for pgsql-admin@arkaria.postgresql.org; Wed, 09 Dec 2020 17:19:26 +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 1kn37e-0005Ka-Jb for pgsql-admin@lists.postgresql.org; Wed, 09 Dec 2020 17:19:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kn37a-0001Zc-0J for pgsql-admin@lists.postgresql.org; Wed, 09 Dec 2020 17:19:26 +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 0B9HJIgs3632845; Wed, 9 Dec 2020 12:19:18 -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: <2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com> References: <074FE83A-E924-4787-9E68-27EB9CE142B3@elevated-dev.com> <3264512.1607456932@sss.pgh.pa.us> <154608A6-0F38-4BE8-B3F4-3E3308691F91@elevated-dev.com> <2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com> Comments: In-reply-to Scott Ribe message dated "Wed, 09 Dec 2020 09:59:32 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3632843.1607534358.1@sss.pgh.pa.us> Date: Wed, 09 Dec 2020 12:19:18 -0500 Message-ID: <3632844.1607534358@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Scott Ribe writes: > Any other suggestions? What could possibly be triggering this GRANT? Ah, I'm sorry, I pointed you at the wrong catalog entirely. It's not pg_default_acl that controls this, it's pg_init_privs. I believe what pg_dump is doing is emitting GRANT commands that replicate the difference between pg_pltemplate's current actual privileges and what is shown for it in pg_init_privs. So you need to make those two things match, in whichever way is easiest. regards, tom lane