relnotes: update item about public schema permission change

Also mention the bootstrap superuser.

Reported-by: Noah Misch
Discussion: https://postgr.es/m/20220628063719[email protected]

diff --git a/doc/src/sgml/release-15.sgml b/doc/src/sgml/release-15.sgml
index 6da3f89d08656c80ce8d4c61978ea74f69f9f83b..47ac329e793491e4ac5ad4ee7a159f142dced447 100644 (file)
--- 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>