From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 12 to 13 migration, the privs error with pg_pltemplate |
Date: | 2020-12-17 18:50:11 |
Message-ID: | 107286.1608231011@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Bruce Momjian <bruce(at)momjian(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Watkins | 2020-12-17 19:24:55 | Grant request |
Previous Message | Bruce Momjian | 2020-12-17 18:40:17 | Re: 12 to 13 migration, the privs error with pg_pltemplate |