From: | Ivan Tsyba <ivantsyba(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Docs about INSERT wait in Read Commited transaction |
Date: | 2022-05-09 01:36:24 |
Message-ID: | CAJQY8UosNct0m0xbD7gkWGs02c0SOZN1DET-Q94jjpV1LrC2SQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Yes, the behavior is documented there. I would suggest to add one sentence
about it to transactions page.
Thank you
пн, 9 трав. 2022, 04:27 користувач David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> пише:
> On Saturday, May 7, 2022, PG Doc comments form <noreply(at)postgresql(dot)org>
> 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.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2022-05-11 00:33:43 | correction |
Previous Message | David G. Johnston | 2022-05-09 01:27:31 | Re: Docs about INSERT wait in Read Commited transaction |