Stephen Frost <sfrost@xxxxxxxxxxx> writes: > I'm not seeing a very simple answer for this, unfortunately. I'm inclined to argue that it was a mistake to include any non-pinned objects in pg_init_privs. The reason initdb leaves some objects unpinned is exactly because they can be dropped and recreated, and that means that their "initial" privileges are not static system properties. We might need to fix pg_dump too, but I think these entries in pg_init_privs should simply not be there. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
