From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
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-20 02:45:02 |
Message-ID: | CAA4eK1Kf8xMR8Ur4BPz2Yok89xqqt4j0nVgH5QC3XXkkgGMWCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 20, 2021 at 3:15 AM Jonathan S. Katz <jkatz(at)postgresql(dot)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.
>
+1 to this list. One enhancement which we might want to consider is:
Improve the performance of updates/deletes on partitioned tables when
only a few partitions are affected (Amit Langote, Tom Lane)
I think this will be quite useful for customers using partitions.
--
With Regards,
Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2021-09-20 02:47:42 | Unintended interaction between bottom-up deletion and deduplication's single value strategy |
Previous Message | Private Information Retrieval(PIR) | 2021-09-20 02:40:37 | Re: Improved PostgreSQL Mathematics Support. |