Horton

Re: First draft of the PG 15 release notes

Noah Misch <noah@leadboat.com>

View thread View on postgr.es
From: Noah Misch <noah@leadboat.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2022-07-02T01:21:28Z
Lists: pgsql-hackers 
On Fri, Jul 01, 2022 at 02:08:00PM -0400, Bruce Momjian wrote:
> On Wed, Jun 29, 2022 at 10:08:08PM -0700, Noah Misch wrote:
> > On Tue, Jun 28, 2022 at 04:35:45PM -0400, Bruce Momjian wrote:

> > > > >       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
> > > > 
> > > > The phrase "old permissions on new objects" doesn't sound right to me, but I'm
> > > > not sure why.  I think you're aiming for the fact that this is just a default;
> > > > one can still change the ACL to anything, including to the old default.  If
> > > > these notes are going to mention the old default like they do so far, I think
> > > > they should also urge readers to understand
> > > > https://www.postgresql.org/docs/devel/ddl-schemas.html#DDL-SCHEMAS-PATTERNS
> > > > before returning to the old default.  What do you think?
> > > 
> > > Agreed, the new text is:
> > > 
> > > 	Users wishing 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.
> > 
> > What do you think about the "should also urge readers ..." part of my message?
> 
> I see your point, that there is no indication of why you might not want
> to restore the old permissions.  I created the attached patch which
> makes two additions to clarify this.

> --- a/doc/src/sgml/release-15.sgml
> +++ b/doc/src/sgml/release-15.sgml
> @@ -63,12 +63,11 @@ Author: Noah Misch <noah@leadboat.com>
>        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 former more-open permissions 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.  This change was made to increase
> -      security.
> +      to have these permissions.
>       </para>
>      </listitem>

Here's what I've been trying to ask: what do you think of linking to
https://www.postgresql.org/docs/devel/ddl-schemas.html#DDL-SCHEMAS-PATTERNS
here?  The release note text is still vague, and the docs have extensive
coverage of the topic.  The notes can just link to that extensive coverage.

Commits

  1. Doc: last minute adjustment to the release notes

  2. Doc: more tweaking of v15 release notes.

  3. Doc: further adjust notes about pg_upgrade_output.d.

  4. Doc: add list of major features to the v15 release notes.

  5. relnotes: update item about public schema permission change

  6. relnotes: update ordered partition scan item

  7. relnotes: add Heikki to UTF8 item

  8. relnotes: improve UTF8 text item in relation to ASCII

  9. relnotes: add null logical replication item

  10. relnotes: adjust several logical replication items and FK text

  11. relnotes: mention non-exclusive backup mode was deprecated

  12. relnotes: add author to in-memory sorts item

  13. relnotes: update for non-exclusive backup mode removal

  14. relnote: improve sorting entries

  15. relnotes: adjustments from Álvaro Herrera

  16. relnotes: update foreign key partition and add sort items

  17. relnotes: more adjustments

  18. relnotes: logical replication permissions checked by subscrib.

  19. relnotes: adjustments

  20. relnotes: remove sequence replication and update 'postgres -C'

  21. relnote: extensive updates

  22. relnotes: "training" -> "trailing"

  23. Standardize references to Zstandard as <productname>

  24. pgstat: Update docs to match the shared memory stats reality.

  25. Raise a WARNING for missing publications.

  26. Skip empty transactions for logical replication.

  27. Optionally disable subscriptions on error.

  28. Allow root-owned SSL private keys in libpq, not only the backend.

  29. Use COPY FREEZE in pgbench for faster benchmark table population.