* David G. Johnston (david.g.johns...@gmail.com) wrote: > On Wed, Mar 2, 2016 at 1:54 PM, Stephen Frost <sfr...@snowman.net> wrote: > > Rather than have two aclitem columns in every catalog, since this > > information is only used by pg_dump and not during normal operation, we > > could use the approach that pg_description took and have an independent > > catalog table which just contains all non-NULL "system" ACLs. We could > > populate it at the bottom of system_views.sql, so that we don't have to > > explicitly think about updating that table whenever there's a change to > > what the default ACLs are. > > > > I don't see any reason it couldn't be used by extensions also, though > > we'd have to do a bit more work on pg_dump to make it actually dump > > out any non-default ACLs for extension-owned objects. > > > > It sounds like this train of thought would resolve this complaint? > > > http://www.postgresql.org/message-id/CADmxfmmz-ATwptaidTSAF0XE=cpeikmyc00sj6t9xf6kcv5...@mail.gmail.com > > Namely allowing users to edit permissions on extension objects and have > those changes dumped and then restored after the dependent CREATE EXTENSION > command is executed during pg_restore. > > Did I interpret that right?
Yes, I was following that thread also (as was Joe, I imagine) and that's the idea. Thanks! Stephen
Description: Digital signature