Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit3c49fa2

Browse files
committed
Check collation when creating partitioned index
When creating a partitioned index, the partition key must be a subsetof the index's columns. But this currently doesn't check that thecollations 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 itwould have to be crafted explicitly and is not something that wouldjust happen by accident.)This patch adds the required collation check. As a result, anypreviously allowed unique index that has a collation mismatch would nolonger 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
1 parentefb8046 commit3c49fa2

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

‎src/backend/commands/indexcmds.c

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -984,10 +984,13 @@ DefineIndex(Oid relationId,
984984
{
985985
if (key->partattrs[i]==indexInfo->ii_IndexAttrNumbers[j])
986986
{
987-
/* Matched the column, now what about the equality op? */
987+
/* Matched the column, now what about thecollation andequality op? */
988988
Oididx_opfamily;
989989
Oididx_opcintype;
990990

991+
if (key->partcollation[i]!=collationObjectId[j])
992+
continue;
993+
991994
if (get_opclass_opfamily_and_input_type(classObjectId[j],
992995
&idx_opfamily,
993996
&idx_opcintype))

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp