From: Bruce Momjian Date: Thu, 14 Jul 2022 19:17:19 +0000 (-0400) Subject: doc: mention that INSERT can block because of unique indexes X-Git-Tag: REL_12_12~37 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ac480b074f4ebad1ae8947b1eeb9790e8925f94e;p=thirdparty%2Fpostgresql.git doc: mention that INSERT can block because of unique indexes Initial patch by David G. Johnston. Reported-by: David G. Johnston Discussion: https://postgr.es/m/CAKFQuwZpbdzceO41VE-xt1Xh8rWRRfgopTAK1wL9EhCo0Am-Sw@mail.gmail.com Backpatch-through: 10 --- diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml index e829c61642d..f2da16867d2 100644 --- a/doc/src/sgml/ref/insert.sgml +++ b/doc/src/sgml/ref/insert.sgml @@ -75,6 +75,11 @@ INSERT INTO table_name [ AS + INSERT into tables that lack unique indexes will + not be blocked by concurrent activity. Tables with unique indexes + might block if concurrent sessions perform actions that lock or modify + rows matching the unique index values being inserted; the details + are covered in . ON CONFLICT can be used to specify an alternative action to raising a unique constraint or exclusion constraint violation error. (See