From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Release 14 Schedule |
Date: | 2021-09-21 02:23:32 |
Message-ID: | 6ffd45f2-a8b2-3dfa-0134-01c13fed3594@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/20/21 2:33 AM, Nikolay Samokhvalov wrote:
> Observability-related improvements are also good and very important for
> the future of DBA operations -- compute_query_id, new pg_stat_**, etc.
>
> Things like new knob idle_session_timeout and restore_command change not
> requiring a restart will be very noticeable too.
I agree on the observability enhancements (the PR draft gives a bunch of
coverage on this) and the usefulness on the knobs.
I think this also highlights that there are a lot of helpful features in
PostgreSQL 14 -- it may be tough to distill them all down into a list
for the release notes themselves. I think typically we try pick 5-7
features to highlight, and we're at about 10 or so proposed.
On the flip side and going off-script, do we need to select only a few
features in the release notes? We can let the press release provide the
general highlights and use that as a spring board to pick out particular
features.
Thanks,
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-09-21 02:29:07 | Re: Estimating HugePages Requirements? |
Previous Message | Jonathan S. Katz | 2021-09-21 02:19:32 | PostgreSQL 14 press release draft |