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-06T02:45:57Z
Lists: pgsql-hackers 
On Tue, Jul 05, 2022 at 07:47:52PM -0400, Bruce Momjian wrote:
> On Tue, Jul  5, 2022 at 02:57:52PM -0700, Noah Misch wrote:
> > Since having too-permissive ACLs is usually symptom-free, I share your
> > forecast about the more-common question.  Expect questions on mailing lists,
> > stackoverflow, etc.  The right way to answer those questions is roughly this:
> > 
> >     > On PostgreSQL 15, my application gets "permission denied for schema
> >     > public".  What should I do?
> > 
> >     You have a choice to make.  The best selection depends on the security
> >     needs of your database.  See
> >     https://www.postgresql.org/docs/devel/ddl-schemas.html#DDL-SCHEMAS-PATTERNS
> >     for a guide to making that choice.
> > 
> > Recommending GRANT to that two-sentence question would be negligent.  One
> > should know a database's lack of security needs before recommending GRANT.
> > This is a key opportunity to have more users make the right decision while
> > their attention is on the topic.
> 
> Yes, I think it is a question of practicality vs. desirability.  We are
> basically telling people they have to do research to get the old
> behavior in their new databases and clusters.

True.  I want to maximize the experience for different classes of database:

1. Databases needing user isolation and unknowingly not getting it.
2. Databases not needing user isolation, e.g. automated test environments.

Expecting all of these DBAs to read a 500-word doc section is failure-prone.
For the benefit of (2), I'm now thinking about adding a release note sentence,
"For a new database having zero need to defend against insider threats,
granting back the privilege yields the PostgreSQL 14 behavior."

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.