We have a set of operational tables that are all partitioned by organization ID (customer ID) in the 100M row range. We also have 3-4 composite indexes on these tables that currently do not include the organization ID. Any queries that reference these tables always provide the organization ID as a discriminator.
We recently started noticing that the query planner sequence scanning the correct partitions, but is not using the indexes. So we decided to run a test by creating a new set of composite indexes that mirror the existing ones but include organization_id as the first column in the composite index. When we create the composite index to include organization ID in the first position, then the planner both selects the correct partitions, AND index scans those partitions.
Is that expected behavior and it is appropriate to include any partition keys as leading columns in any indexes on a partitioned table?
One additional piece of information that may or may not be relevant: a couple weeks ago we upgraded from PG 16.1 to 16.3. In the release notes for 16.2, I did see some fixes pertaining to indexes on partitioned tables and collations. I couldn't find information on the actual fixes (my inexperience digging into PG support).
I'm happy to provide some simple examples to illustrate what we are seeing if the behavior I'm describing is not expected.
Thanks,
We recently started noticing that the query planner sequence scanning the correct partitions, but is not using the indexes. So we decided to run a test by creating a new set of composite indexes that mirror the existing ones but include organization_id as the first column in the composite index. When we create the composite index to include organization ID in the first position, then the planner both selects the correct partitions, AND index scans those partitions.
Is that expected behavior and it is appropriate to include any partition keys as leading columns in any indexes on a partitioned table?
One additional piece of information that may or may not be relevant: a couple weeks ago we upgraded from PG 16.1 to 16.3. In the release notes for 16.2, I did see some fixes pertaining to indexes on partitioned tables and collations. I couldn't find information on the actual fixes (my inexperience digging into PG support).
I'm happy to provide some simple examples to illustrate what we are seeing if the behavior I'm describing is not expected.
Thanks,
Bill Kaper
