Type: | bool |
Default: | off |
Context: | user |
Restart: | false |
Since: | 11 |
Enables or disables the query planner's use of partitionwise join, which allows a join between partitioned tables to be performed by joining the matching partitions. Partitionwise join currently applies only when the join conditions include all the partition keys, which must be of the same data type and have one-to-one matching sets of child partitions. With this setting enabled, the number of nodes whose memory usage is restricted by work_mem appearing in the final plan can increase linearly according to the number of partitions being scanned. This can result in a large increase in overall memory consumption during the execution of the query. Query planning also becomes significantly more expensive in terms of memory and CPU. The default value is off
.
On StackOverflow
On pgsql-hackers
- Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different.
- apply_scanjoin_target_to_paths and partitionwise join
- Re: Wrong result when enable_partitionwise_join is on if collation of PartitionKey and Column is different.
- Re: Memory consumed by paths during partitionwise join planning
- Re: A problem about partitionwise join