multi-column-partitioning (GN018)

Automatic fix is not available.

What it does

Checks for partitioning with more than one column.

Why not?

One of the main reasons to use partitioning is the improved performance achieved by partition pruning. Pruning in a multi-column partitioned table can easily be sub-optimal, leading to scanning of unnecessary partitions.

When should you?

If you know what you are doing and have a good reason to do so. Just don't use multi-column partitioning without deep consideration and knowledge of its intrinsics. An example of what could go wrong is why-isnt-postgres-multicolumn-partition-pruning-smarter-than-this

Use instead:

Sub-partitioning.