Re: PostgreSQL 16 release announcement draft - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: PostgreSQL 16 release announcement draft
Date
Msg-id 01a0939a-6d0c-34b0-13cb-c145987fae18@postgresql.org
Whole thread Raw
In response to Re: PostgreSQL 16 release announcement draft  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: PostgreSQL 16 release announcement draft
List pgsql-hackers
On 8/23/23 8:02 AM, David Rowley wrote:
> On Wed, 23 Aug 2023 at 22:21, jian he <jian.universality@gmail.com> wrote:
>>
>>>>>
>> 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, utilize incremental sorts for
>> `SELECT DISTINCT` queries, and execute window functions more efficiently. It
>> also introduces `RIGHT` and `OUTER` "anti-joins", which enable users to identify
>> rows not present in a joined table.
>>>>>
>>
>> I think "utilize incremental sorts is for" something like select
>> my_avg(distinct one),my_sum(one) from (values(1),(3)) t(one);
>> so it's not the same as `SELECT DISTINCT` queries?
>> ref: https://git.postgresql.org/cgit/postgresql.git/commit/?id=1349d2790bf48a4de072931c722f39337e72055e
> 
> The incremental sorts for DISTINCT will likely be a reference to
> 3c6fc5820, so, not the same thing as 1349d2790.  I don't see anything
> there relating to 1349d2790.

We could add something about 1349d2790 -- do you have suggested wording?

>> also
>> <<<< "the query planner ....., and execute window functions more efficiently."
>> since the query planner doesn't execute anything. probably "and
>> optimize window functions execution"?
> 
> Yeah, that or "and optimize window functions so they execute more
> efficiently" is likely an improvement there.

Modified. See updated announcement, with other incorporated changes.

Reminder that the window to submit changes closes at **August 26, 12:00 
UTC**.

Thanks,

Jonathan


Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Oversight in reparameterize_path_by_child leading to executor crash
Next
From: Peter Eisentraut
Date:
Subject: Re: Make all Perl warnings fatal