How partition-wise joins and aggregates improve Postgres query performance

In E81 of “5mins of Postgres” we're talking about how partition-wise joins can improve your Postgres query performance. We also look at partitionwise-aggregates and their impact on query planning time and query execution time.

*Learn more about pganalyze:*

*Check out the pganalyze library for eBooks, webinars, and more:*

📑 *What we have discussed in this episode of 5mins of Postgres:*

*Partitioning as a query optimization strategy? - by Ashutosh Bapat*

*Ashutosh Bapat - PostgreSQL Person of the Week*

*Partition-wise joins: "divide and conquer" for joins between partitioned table - by Ashutosh Bapat*

*Allow partitionwise joins in more cases - postgresql commit*

*Partitioning use cases with PostgreSQL: partitionwise aggregate - by Adrien Nayrat*

*Adrien Nayrat on Twitter*

*5mins of Postgres E18: Partition pruning, prepared statements and generic vs custom query plans*

*5mins of Postgres E22: Reducing AWS Aurora I/O costs with table partitioning & understanding partition pruning*

*Partitioning in Postgres and the risk of high partition counts*

[qiweishen]

Very interesting! Curious does the unpartitioned table has an index on the partition by column? If not, is the join by index better than partition-wise join