From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Release 14 Schedule |
Date: | 2021-09-21 06:49:36 |
Message-ID: | 93f7fd39-d625-b8a0-13c8-0c83571dfd9c@archidevsys.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21/09/21 14:23, Jonathan S. Katz wrote:
> 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
>
I suggest that if there are 7 or more, then possibly you should group
them under 2 or 3 headings.
That way it will not look quite so intimidating, and people have a
framework to give them perspective. Also makes it easier for people to
focus on the highlights that they might consider the most important to
themselves.
Cheers,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2021-09-21 06:50:31 | Re: proposal: possibility to read dumped table's name from file |
Previous Message | Amit Kapila | 2021-09-21 06:38:28 | Re: Logical replication timeout problem |