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. On Sun, Sep 19, 2021 at 2:45 PM Jonathan S. Katz <jk...@postgresql.org> wrote: > 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? > > > > . Allow extended statistics on column expressions; > > . Memoize node which can improve speed of nested loop joins; > > . Allow use of LZ4 compression for faster access to TOASTed fields; > > . JSONB and H-store types may be subscripted, as may be participating > data types provided by extensions. > > . Many improvements to performance of VACUUM; > > > > Maybe these?? > > I would propose a few different ones. I'm looking at the overall breadth > of user impact as I propose these and the reactions I've seen in the field. > > - General performance improvements for databases with multiple > connections (the MVCC snapshot work). > > - The reduction in bloat on frequently updated B-trees; that was a > longstanding complaint against PostgreSQL that was resolved. > > - I agree with the JSON improvements; I'd bucket this in data types and > include the support of multiranges. > > - Logical decoding / replication received some significant performance > improvements > > - Many improvements in query parallelism. One that stands out is how > parallel queries can be leveraged using FDWs now, in particular the > postgres_fdw. > > - I agree with VACUUM suggestion as well. > > 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. > > Thanks, > > Jonathan > >
