Commit6959e97

committed

doc: mention that INSERT can block because of unique indexes

Initial patch by David G. Johnston.Reported-by: David G. JohnstonDiscussion:https://postgr.es/m/CAKFQuwZpbdzceO41VE-xt1Xh8rWRRfgopTAK1wL9EhCo0Am-Sw@mail.gmail.comBackpatch-through: 10

1 parent3e071b2 commit6959e97Copy full SHA for 6959e97

File tree

-0

lines changed

-0

lines changed

Lines changed: 5 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -75,6 +75,11 @@ INSERT INTO <replaceable class="parameter">table_name</replaceable> [ AS <replac`
`75`	`75`	`</para>`
`76`	`76`
`77`	`77`	`<para>`
	`78`	`+ <command>INSERT</command> into tables that lack unique indexes will`
	`79`	`+ not be blocked by concurrent activity. Tables with unique indexes`
	`80`	`+ might block if concurrent sessions perform actions that lock or modify`
	`81`	`+ rows matching the unique index values being inserted; the details`
	`82`	`+ are covered in <xref linkend="index-unique-checks"/>.`
`78`	`83`	`<literal>ON CONFLICT</literal> can be used to specify an alternative`
`79`	`84`	`action to raising a unique constraint or exclusion constraint`
`80`	`85`	`violation error. (See <xref linkend="sql-on-conflict"/> below.)`

Comments

(0)