aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2015-07-26 18:20:41 +0200
committerAndres Freund <andres@anarazel.de>2015-07-26 18:20:48 +0200
commit13d0053f98390ad17e373cefb95e27273c0c345c (patch)
treee2436b800ab9f6f76b527dd45455ae39542be337 /src/backend/executor/nodeModifyTable.c
parentb17ae36ba9521014c5ae30cb3a3f77c439b41bb3 (diff)
downloadpostgresql-13d0053f98390ad17e373cefb95e27273c0c345c.tar.gz
postgresql-13d0053f98390ad17e373cefb95e27273c0c345c.zip
Check the relevant index element in ON CONFLICT unique index inference.
ON CONFLICT unique index inference had a thinko that could affect cases where the user-supplied inference clause required that an attribute match a particular (user specified) collation and/or opclass. infer_collation_opclass_match() has to check for opclass and/or collation matches and that the attribute is in the list of attributes or expressions known to be in the definition of the index under consideration. The bug was that these two conditions weren't necessarily evaluated for the same index attribute. Author: Peter Geoghegan Discussion: CAM3SWZR4uug=WvmGk7UgsqHn2MkEzy9YU-+8jKGO4JPhesyeWg@mail.gmail.com Backpatch: 9.5, where ON CONFLICT was introduced
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions