Add some isolation tests for CLUSTER
Michael Paquier <michael@paquier.xyz>
Add some isolation tests for CLUSTER This commit adds two isolation tests for CLUSTER, using: - A normal table, making sure that CLUSTER blocks and completes if the table is locked by a concurrent session. - A partitioned table with a partition owned by a different user. If the partitioned table is locked by a concurrent session, CLUSTER on the partitioned table should block. If the partition owned by a different user is locked, CLUSTER on its partitioned table should complete and skip the partition. 3f19e17 has added an early check to ignore such a partition with a SQL regression test, but this was not checking that CLUSTER should not block. Discussion: https://postgr.es/m/YlqveniXn9AI6RFZ@paquier.xyz
Files
| Path | Change | +/− |
|---|---|---|
| src/test/isolation/expected/cluster-conflict.out | added | +19 −0 |
| src/test/isolation/expected/cluster-conflict-partition.out | added | +35 −0 |
| src/test/isolation/isolation_schedule | modified | +2 −0 |
| src/test/isolation/specs/cluster-conflict-partition.spec | added | +37 −0 |
| src/test/isolation/specs/cluster-conflict.spec | added | +30 −0 |
Discussion
- CLUSTER on partitioned index 37 messages · 2020-10-28 → 2022-04-26