Commitfaba259

committed

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.comBackpatch-through: 13

1 parentd26997c commitfaba259Copy full SHA for faba259

File tree

+14

-0

lines changed

+14

-0

lines changed

Lines changed: 9 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -556,6 +556,15 @@ INSERT INTO <replaceable class="parameter">table_name</replaceable> [ AS <replac`
`556`	`556`	`</para>`
`557`	`557`	`</tip>`
`558`	`558`
	`559`	`+ <warning>`
	`560`	`+ <para>`
	`561`	`+ While <command>CREATE INDEX CONCURRENTLY</command> or <command>REINDEX`
	`562`	`+ CONCURRENTLY</command> is running on a unique index, <command>INSERT`
	`563`	`+ ... ON CONFLICT</command> statements on the same table may unexpectedly`
	`564`	`+ fail with a unique violation.`
	`565`	`+ </para>`
	`566`	`+ </warning>`
	`567`	`+`
`559`	`568`	`</refsect2>`
`560`	`569`	`</refsect1>`
`561`	`570`

Lines changed: 5 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -634,6 +634,11 @@ get_relation_foreign_keys(PlannerInfo root, RelOptInfo rel,`
`634`	`634`	`* the purposes of inference. If no opclass (or collation) is specified, then`
`635`	`635`	`* all matching indexes (that may or may not match the default in terms of`
`636`	`636`	`* each attribute opclass/collation) are used for inference.`
	`637`	`+ *`
	`638`	`+ * Note: during index CONCURRENTLY operations, different transactions may`
	`639`	`+ * reference different sets of arbiter indexes. This can lead to false unique`
	`640`	`+ * constraint violations that wouldn't occur during normal operations. For`
	`641`	`+ * more information, see insert.sgml.`
`637`	`642`	`*/`
`638`	`643`	`List*`
`639`	`644`	`infer_arbiter_indexes(PlannerInfo*root)`

Comments

(0)