Check collation when creating partitioned index
authorPeter Eisentraut <peter@eisentraut.org>
Fri, 1 Dec 2023 14:48:06 +0000 (15:48 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Fri, 1 Dec 2023 15:05:41 +0000 (16:05 +0100)
commita11c9c42ea3193ff7a977764788bda43ebb07b35
tree17a9bc7cb206fe745d2ea6c90329306088b6032e
parent5b2dcead39904ae56e2c17cb5c7a14e6f255790c
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
src/backend/commands/indexcmds.c