1
0
mirror of https://github.com/postgres/postgres.git synced 2025-11-09 06:21:09 +03:00

Doc: cover index CONCURRENTLY causing errors in INSERT ... ON CONFLICT.

Author: Mikhail Nikalayeu <mihailnikalayeu@gmail.com>
Reviewed-by: Noah Misch <noah@leadboat.com>
Discussion: https://postgr.es/m/CANtu0ojXmqjmEzp-=aJSxjsdE76iAsRgHBoK0QtYHimb_mEfsg@mail.gmail.com
Backpatch-through: 13
This commit is contained in:
Noah Misch
2025-11-03 12:57:09 -08:00
parent e7ccb247b3
commit 8b18ed6dfb
2 changed files with 14 additions and 0 deletions

View File

@@ -789,6 +789,11 @@ find_relation_notnullatts(PlannerInfo *root, Oid relid)
* the purposes of inference. If no opclass (or collation) is specified, then
* all matching indexes (that may or may not match the default in terms of
* each attribute opclass/collation) are used for inference.
*
* Note: during index CONCURRENTLY operations, different transactions may
* reference different sets of arbiter indexes. This can lead to false unique
* constraint violations that wouldn't occur during normal operations. For
* more information, see insert.sgml.
*/
List *
infer_arbiter_indexes(PlannerInfo *root)