Thread: pgsql: Check collation when creating partitioned index
Check collation when creating partitioned index When creating a partitioned index, the partition key must be a subset of the index's columns. But this currently doesn't check that the collations between the partition key and the index definition match. So you can construct a unique index that fails to enforce uniqueness. (This would most likely involve a nondeterministic collation, so it would have to be crafted explicitly and is not something that would just happen by accident.) This patch adds the required collation check. As a result, any previously allowed unique index that has a collation mismatch would no longer be allowed to be created. Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://www.postgresql.org/message-id/flat/3327cb54-f7f1-413b-8fdb-7a9dceebb938%40eisentraut.org Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3c49fa2aff2c2e4ec612c97e2c44b928c8809fae Modified Files -------------- src/backend/commands/indexcmds.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)