From: | jian he <jian(dot)universality(at)gmail(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | 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-23 10:20:49 |
Message-ID: | CACJufxGNvaSdEk_BWBpMyb=p_0uhs6RMtH3tdc6TeweOdm51DQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>
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
also
<<<< "the query planner ....., and execute window functions more efficiently."
since the query planner doesn't execute anything. probably "and
optimize window functions execution"?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-08-23 10:46:45 | Re: Remove distprep |
Previous Message | shveta malik | 2023-08-23 10:07:59 | Re: Synchronizing slots from primary to standby |