On Wed, Sep 22, 2021 at 12:00:07PM -0400, Jonathan S. Katz wrote: > On 9/22/21 11:15 AM, Magnus Hagander wrote: > > On Wed, Sep 22, 2021 at 5:12 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > >> "Jonathan S. Katz" <jk...@postgresql.org> writes: > >>> On 9/19/21 12:32 PM, Justin Pryzby wrote: > >>>> On Sat, Sep 18, 2021 at 01:37:19PM -0400, Tom Lane wrote: > >>>>> We don't yet have a list-of-major-features for the v14 release notes. > >>>>> Anybody care to propose one? > >> > >>> I can try proposing some wording on this in a bit; I'm working on the > >>> overdue draft of the press release, and thought I'd chime in here first. > >> > >> I looked over Jonathan's draft press release [1] and tried to boil it down > >> to our usual ten-or-so bullet points for the release notes' introductory > >> paragraph. I ended up with this (didn't bother with markup yet): > >> > >> ----- > >> Stored procedures can now return data via OUT parameters. > >> > >> The SQL-standard SEARCH and CYCLE options for common table expressions > >> have been implemented. > >> > >> Range types have been extended by adding multiranges, which allow > >> representation of noncontiguous data ranges. > >> > >> Subscripting can now be applied to any data type for which it is a useful > >> notation, not only arrays. In this release, JSONB and hstore have gained > >> subscripting operators. > >> > >> Numerous performance improvements have been made for parallel queries, > >> heavily-concurrent workloads, partitioned tables, logical replication, and > >> vacuuming. Notably, foreign data wrappers can now make use of query > >> parallelism. > > > > "foreign data wrappers and stored procedures/functions" maybe? > > +1 > > >> B-tree index updates are managed more efficiently, reducing index bloat. > >> > >> Extended statistics can now be collected on expressions, allowing > >> better planning results for complex queries. > >> > >> libpq now has the ability to pipeline multiple queries, which can boost > >> throughput over high-latency connections. > >> > >> TOAST data can optionally be compressed with LZ4 instead of the traditional > >> pglz algorithm. > >> ----- > >> > >> I'm not entirely sure that the TOAST item should make the cut, > > > > I think it should be t here. > > Leaning towards keeping it. If we subbed it, I'd suggest a statement on > the monitoring/observability improvements. > > >> but I feel fairly good about the rest of this list. Thoughts? > > > > I have a feeling emergency mode vacuum fits on that list. Not in the > > press release, but in the major features list of the release notes. > > Given some recent news I saw floating around, I'd agree with this. > > My suggestion on ordering: > > - Numerous performance ... > - B-tree... > - Subscripting ... > - Range types ... > - Stored ... > - Extended ... > - SEARCH / CYCLE ... > - libpq ... > - TOAST ... > (- emergency mode vacuum ...)
Maybe group the features together into types of features, similar to v11/v12: https://www.postgresql.org/docs/12/release-12.html SQL features: SEARCH/CYLCE, subcripting, range, ... Performance improvements in btree, vacuum, toast... ... -- Justin
