From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, chelseadole(at)gmail(dot)com |
Subject: | Re: PostgreSQL 16 release announcement draft |
Date: | 2023-08-24 14:32:02 |
Message-ID: | 8cdb760c-2d15-bfde-9a44-fe58e28b05c1@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/23/23 5:07 PM, David Rowley wrote:
> On Thu, 24 Aug 2023 at 05:55, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>> We could add something about 1349d2790 -- do you have suggested wording?
>
> I think it's worth a mention. See the text added in square brackets below:
>
> PostgreSQL 16 improves the performance of existing PostgreSQL functionality
> through new query planner optimizations. In this latest release, the query
> planner can parallelize `FULL` and `RIGHT` joins, [generate more
> optimal plans for
> queries containing aggregate functions with a `DISTINCT` or `ORDER BY` clause,]
> utilize incremental sorts for `SELECT DISTINCT` queries, and optimize
> window function
> executions so they execute more efficiently. It also introduces
> `RIGHT` and `OUTER`
> "anti-joins", which enable users to identify rows not present in a joined table.
I added this in mostly verbatim. I'm concerned the sentence is a bit
long, but we could break it up into two: (1) with the new JOIN
capabilities and (2) with the optimizations.
Jonathan
Attachment | Content-Type | Size |
---|---|---|
release.en.md | text/plain | 9.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2023-08-24 15:15:33 | Checks in RegisterBackgroundWorker.() |
Previous Message | Jehan-Guillaume de Rorthais | 2023-08-24 14:26:53 | Re: EBCDIC sorting as a use case for ICU rules |