diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2023-12-01 15:48:06 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2023-12-01 16:05:41 +0100 |
| commit | a11c9c42ea3193ff7a977764788bda43ebb07b35 (patch) | |
| tree | 17a9bc7cb206fe745d2ea6c90329306088b6032e /src/backend/access/gist/gistvalidate.c | |
| parent | 5b2dcead39904ae56e2c17cb5c7a14e6f255790c (diff) | |
| download | postgresql-a11c9c42ea3193ff7a977764788bda43ebb07b35.tar.gz postgresql-a11c9c42ea3193ff7a977764788bda43ebb07b35.zip | |
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
Diffstat (limited to 'src/backend/access/gist/gistvalidate.c')
0 files changed, 0 insertions, 0 deletions