| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "ivantsyba(at)gmail(dot)com" <ivantsyba(at)gmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Docs about INSERT wait in Read Commited transaction |
| Date: | 2022-05-09 01:27:31 |
| Message-ID: | CAKFQuwbkCJ=BBGtunXMEdRCEpXgWu3jr-Fw-hSFKdJMHq-owTw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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 | Ivan Tsyba | 2022-05-09 01:36:24 | Re: Docs about INSERT wait in Read Commited transaction |
| Previous Message | PG Doc comments form | 2022-05-07 22:12:06 | Docs about INSERT wait in Read Commited transaction |