Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <3632844.1607534358@sss.pgh.pa.us>
Date: Wed, 9 Dec 2020 10:33:31 -0700
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <68634B7E-3AD0-42A3-9A2D-EC3988E755E4@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>
 <3632844.1607534358@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk

> On Dec 9, 2020, at 10:19 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> Scott Ribe <scott_ribe@elevated-dev.com> writes:
>> Any other suggestions? What could possibly be triggering this GRANT?
>=20
> 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.

OK, now *THAT* turned up a lot of suspicious entries. It will be a bit =
before I can try straightening that out. But there's a lot of tables in =
pg_catalog that have privs listed for the user in question.