-
- Downloads
Clean up a few failures to set collation fields in expression nodes.
I'm not sure these have any non-cosmetic implications, but I'm not sure they don't, either. In particular, ensure the CaseTestExpr generated by transformAssignmentIndirection to represent the base target column carries the correct collation, because parse_collate.c won't fix that. Tweak lsyscache.c API so that we can get the appropriate collation without an extra syscache lookup.
Showing
- src/backend/optimizer/path/pathkeys.c 1 addition, 2 deletionssrc/backend/optimizer/path/pathkeys.c
- src/backend/optimizer/plan/createplan.c 2 additions, 0 deletionssrc/backend/optimizer/plan/createplan.c
- src/backend/optimizer/util/clauses.c 1 addition, 1 deletionsrc/backend/optimizer/util/clauses.c
- src/backend/optimizer/util/predtest.c 4 additions, 0 deletionssrc/backend/optimizer/util/predtest.c
- src/backend/parser/parse_coerce.c 2 additions, 0 deletionssrc/backend/parser/parse_coerce.c
- src/backend/parser/parse_target.c 27 additions, 4 deletionssrc/backend/parser/parse_target.c
- src/backend/utils/adt/ruleutils.c 4 additions, 2 deletionssrc/backend/utils/adt/ruleutils.c
- src/backend/utils/cache/lsyscache.c 6 additions, 32 deletionssrc/backend/utils/cache/lsyscache.c
- src/include/utils/lsyscache.h 2 additions, 3 deletionssrc/include/utils/lsyscache.h
Loading
Please register or sign in to comment