From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: Scott Ribe <scott_ribe@elevated-dev.com>,
        Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate
In-reply-to: <20201217184017.GA23245@momjian.us>
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> <20201217184017.GA23245@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Thu, 17 Dec 2020 13:40:17 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <107285.1608231011.1@sss.pgh.pa.us>
Date: Thu, 17 Dec 2020 13:50:11 -0500
Message-ID: <107286.1608231011@sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> On Wed, Dec  9, 2020 at 12:19:18PM -0500, Tom Lane wrote:
>> 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.

> Should pg_dump or pg_upgrade be detecting and reporting these things,
> rather than requiring this analysis by the user?

It's a little premature to be considering that when we still haven't
identified exactly what the problem is.

			regards, tom lane