Re: PostgreSQL 16 release announcement

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Dave Cramer <davecramer(at)postgres(dot)rocks>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Advocacy <pgsql-advocacy(at)lists(dot)postgresql(dot)org>, chelseadole(at)gmail(dot)com
Subject: Re: PostgreSQL 16 release announcement
Date: 2023-08-23 17:55:38
Message-ID: b742d015-1c82-dfd2-5021-14a15341535b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 8/21/23 7:07 AM, Dave Cramer wrote:
>
>
>
> On Mon, 21 Aug 2023 at 05:32, Daniel Gustafsson <daniel(at)yesql(dot)se
> <mailto:daniel(at)yesql(dot)se>> wrote:
>
> > On 19 Aug 2023, at 21:39, Jonathan S. Katz <jkatz(at)postgresql(dot)org
> <mailto:jkatz(at)postgresql(dot)org>> wrote:
>
> > It's possible we missed or incorrectly stated something, so
> please provide feedback if we did so.
>
>
> What does the improvements to access control have to do with large work
> loads ?

This took me a moment to realize what you were referring to because you
didn't provide the sentence in question.

The theme is built around the changes in the host configuration files
that allow for regular expressions and includes, which, from discussing
with users, benefits people who are managing larger fleets of PostgreSQL.

That said, I see the confusion around the wording. I've changed it to
this below, and attached the latest copy based on other feedback.

==snip==
and greater flexibility in
defining access control rules for management of policies across large
fleets.
==snip==

Reminder that the window to submit changes closes at **August 26, 12:00
UTC**.

Thanks,

Jonathan

Attachment Content-Type Size
release.en.md text/plain 9.2 KB

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Steve Rezhener 2023-08-25 00:33:20 2023 sql.saturday.siliconvalley event is looking for speakers on postgres topics
Previous Message Dave Cramer 2023-08-21 11:07:18 Re: PostgreSQL 16 release announcement