RealGreenDragon opened a new pull request, #32597:
URL: https://github.com/apache/superset/pull/32597

   ### SUMMARY
   This PR bumps to 
[postgresql:16](https://hub.docker.com/layers/library/postgres/16/images/sha256-295787823185868c4679563715b0a7a07309387f3836117f1b0984d1bfc2bd24)
 image version in Dockerfile and GH workflows.
   
   Also this PR bumps [Helm Chart 
postgresql](https://github.com/bitnami/charts/tree/main/bitnami/postgresql) to 
[v13.4.4](https://github.com/bitnami/charts/blob/main/bitnami/postgresql/CHANGELOG.md#1344-2024-02-01)
 (latest v13 release) as it uses PostgreSQL 16 (declared 
[here](https://github.com/bitnami/charts/pull/19587) and 
[here](https://github.com/bitnami/charts/tree/main/bitnami/postgresql/#to-1300)).
   
   PostgreSQL 16.0 change log: https://www.postgresql.org/docs/release/16.0/
   
   From PostgreSQL release 
[news](https://www.postgresql.org/about/news/postgresql-16-released-2715/):
   > 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 better 
optimized plans for queries that use aggregate functions with a DISTINCT or 
ORDER BY clause, utilize incremental sorts for SELECT DISTINCT queries, and 
optimize window functions so they execute more efficiently. It also improves 
RIGHT and OUTER "anti-joins", which enables users to identify rows not present 
in a joined table.
   
   Documentation has been updated accordingly as done in #24147 and #19790 .
   
   Inspired by discussion #27546 .
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to