postgres.git / summary / log / commit / refs

commit    5ea92769aa767a87eed74f591540f03b6f260660
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Thu Jul 14 19:17:19 2022 +0000
First released in: 16.0, 10.22, 11.17, 12.12, 13.8, 14.5, 15.0

    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


doc/src/sgml/ref/insert.sgml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml index 844e0d9f62b..77df65f090e 100644 --- a/doc/src/sgml/ref/insert.sgml +++ b/doc/src/sgml/ref/insert.sgml @@ -75,6 +75,11 @@ INSERT INTO <replaceable class="parameter">table_name</replaceable> [ AS <replac </para> <para> + <command>INSERT</command> 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 <xref linkend="index-unique-checks"/>. <literal>ON CONFLICT</literal> can be used to specify an alternative action to raising a unique constraint or exclusion constraint violation error. (See <xref linkend="sql-on-conflict" [parent: 9d352c4448e9]