diff options
author | Bruce Momjian | 2022-06-28 20:35:32 +0000 |
---|---|---|
committer | Bruce Momjian | 2022-06-28 20:35:32 +0000 |
commit | f5135d2aba87f59944bdab4f54129fc43a3f03d0 (patch) | |
tree | 19e03259f2ca33eaecd9db700c215e14b7a1d89e | |
parent | c1d033fcb5ecf306241cd729d1edcaa846456335 (diff) |
relnotes: update item about public schema permission change
Also mention the bootstrap superuser.
Reported-by: Noah Misch
Discussion: https://postgr.es/m/[email protected]
-rw-r--r-- | doc/src/sgml/release-15.sgml | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml index 6da3f89d08..47ac329e79 100644 --- a/doc/src/sgml/release-15.sgml +++ b/doc/src/sgml/release-15.sgml @@ -63,13 +63,11 @@ Author: Noah Misch <[email protected]> permissions on the <literal>public</literal> schema has not been changed. Databases restored from previous Postgres releases will be restored with their current permissions. Users wishing - to have the old permissions on new objects will need to grant + to have the former permissions will need to grant <literal>CREATE</literal> permission for <literal>PUBLIC</literal> on the <literal>public</literal> schema; this change can be made on <literal>template1</literal> to cause all new databases - to have these permissions. <literal>template1</literal> - permissions for <application>pg_dumpall</application> and - <application>pg_upgrade</application>? + to have these permissions. </para> </listitem> @@ -85,7 +83,7 @@ Author: Noah Misch <[email protected]> </para> <para> - Previously it was the literal user name of the database owner. + Previously it was the literal user name of the bootstrap superuser. Databases restored from previous Postgres releases will be restored with their current owner specification. </para> |