Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nnsBX-0006Px-Ey for pgsql-docs@arkaria.postgresql.org; Mon, 09 May 2022 01:27:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nnsBW-0002EQ-9I for pgsql-docs@arkaria.postgresql.org; Mon, 09 May 2022 01:27:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nnsBV-0002Dk-WE for pgsql-docs@lists.postgresql.org; Mon, 09 May 2022 01:27:38 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nnsBT-0006Jm-Cf for pgsql-docs@lists.postgresql.org; Mon, 09 May 2022 01:27:37 +0000 Received: by mail-ej1-x62d.google.com with SMTP id gh6so24036131ejb.0 for ; Sun, 08 May 2022 18:27:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=oxEaEY73MT2zm+lhdPOckhSAIoOaMkYF26eoeElRI5M=; b=WuzuKpYVLcaEkC9qV0YA5KEe1Wb9K0OoKPvZF8XK94oAJpT/xign139kr0jwmEyrVp qIbreRukz6wf+wgf1eKksElH1ojxwOvKPD0CEGX0X4IUsLcsI9qGCV6iPAa2S5kaLKad G21G1/Of1t/sR25bKi8fUCrhiVmS34Ogss59yPlqU6OW9tCR9flXWzUjnTFkiGZrWZbZ 8t28R8SPv0Qhj3XBfht68kU8csgX7hpnpB/e5VhtRGUscONPzMqXueXcEz2EB1XSRAMu 2W399MVJT9/Bz6TYioR3Qa6UbBmEo1gmUB1bqrgk4siKEPYDDb8s7UdaRoPm2dW0gpVM LhAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=oxEaEY73MT2zm+lhdPOckhSAIoOaMkYF26eoeElRI5M=; b=4HG/7fxc84GOtXmFXIv05hMn7PLyuuchofCQ9DzAhuSS8BrxexayneC/twypdC5iB/ wsdzR0CPwZFXgP60ds7OVDoWsGjzd73zTDf5ScYwUzGsBtrktvs5+f8nMyPZvDiAjIrI 16Hjo8pZBG7K1T9vZaxyCwSFW+t8kP4ZqYPdwcjFp53D3ZlWO3VicSrSYXjG4188Ufif kR2dmu7ZofIDxlVzKBefucbyL7XnCF16oV1m8gHAt6KHVIZzXaW/7gADHSgskIGACw74 Wv0m5OYL60+eC8bnFTkVND8Do0qoyGavrRx4Tfkk5717UdDY9z/LxvHznLpZYk+3LP3/ tQDg== X-Gm-Message-State: AOAM530JCF6ZbLzGC9KTVJMWtZjB6rG81W9UQCBvIeZGbe40A6ICPUAR ZzFD7D+TlN+P0X6pyLsw/psFcQIgTEdUV5/+S/E= X-Google-Smtp-Source: ABdhPJyf00E77j0BGem/6vCoFsabN0jVAXuwKskZ3aPbZYZYqcRVuGHtlOzBbIMVoTCmI3bCnL/zGjvYH6Kj7s29Oak= X-Received: by 2002:a17:907:d22:b0:6f4:8766:2042 with SMTP id gn34-20020a1709070d2200b006f487662042mr12669458ejc.259.1652059652337; Sun, 08 May 2022 18:27:32 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:640c:2bc8:b0:15b:bd92:6856 with HTTP; Sun, 8 May 2022 18:27:31 -0700 (PDT) In-Reply-To: <165196152696.668.3099435890630131836@wrigleys.postgresql.org> References: <165196152696.668.3099435890630131836@wrigleys.postgresql.org> From: "David G. Johnston" Date: Sun, 8 May 2022 18:27:31 -0700 Message-ID: Subject: Re: Docs about INSERT wait in Read Commited transaction To: "ivantsyba@gmail.com" , "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000b9b51905de8a1c3a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b9b51905de8a1c3a Content-Type: text/plain; charset="UTF-8" On Saturday, May 7, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/transaction-iso.html > Description: > > Hello > I've noticed, if two transactions in read committed mode are trying to > insert same value to unique column, second transaction INSERT will wait for > the first transaction commit or rollback. Can't see this behavior > explicitly > stated in the doc about transaction isolation modes. > > It is documented elsewhere: https://www.postgresql.org/docs/current/index-unique-checks.html David J. --000000000000b9b51905de8a1c3a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Saturday, May 7, 2022, PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on the w= ebsite:

Page: https://www.postgresql.org/docs/14/transaction-iso.ht= ml
Description:

Hello
I've noticed, if two transactions in read committed mode are trying to<= br> insert same value to unique column, second transaction INSERT will wait for=
the first transaction commit or rollback. Can't see this behavior expli= citly
stated in the doc about transaction isolation modes.


It is documented elsewhere:

=

David J.
=C2=A0
--000000000000b9b51905de8a1c3a--