Re: 12 to 13 migration, the privs error with pg_pltemplate - Mailing list pgsql-admin

From Bruce Momjian
Subject Re: 12 to 13 migration, the privs error with pg_pltemplate
Date
Msg-id 20201217184017.GA23245@momjian.us
Whole thread Raw
In response to Re: 12 to 13 migration, the privs error with pg_pltemplate  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 12 to 13 migration, the privs error with pg_pltemplate  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Wed, Dec  9, 2020 at 12:19:18PM -0500, Tom Lane wrote:
> Scott Ribe <scott_ribe@elevated-dev.com> 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.

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

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Error in getNextException No space left on device Call getNextException to see other errors in the batch. (java.sql.BatchUpdateException)
Next
From: Tom Lane
Date:
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate