]> granicus.if.org Git - postgresql/commit
Check the relevant index element in ON CONFLICT unique index inference.
authorAndres Freund <andres@anarazel.de>
Sun, 26 Jul 2015 16:20:41 +0000 (18:20 +0200)
committerAndres Freund <andres@anarazel.de>
Sun, 26 Jul 2015 16:20:48 +0000 (18:20 +0200)
commit13d0053f98390ad17e373cefb95e27273c0c345c
treee2436b800ab9f6f76b527dd45455ae39542be337
parentb17ae36ba9521014c5ae30cb3a3f77c439b41bb3
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
src/backend/optimizer/util/plancat.c
src/test/regress/expected/insert_conflict.out
src/test/regress/sql/insert_conflict.sql