| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "lebedewwasya(at)gmail(dot)com" <lebedewwasya(at)gmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 13.2.2. Repeatable Read Isolation Level # |
| Date: | 2024-07-16 14:13:49 |
| Message-ID: | CAKFQuwbLj=V8Lo20D2E+hxZyhukim3R6zTWk2ojOcKn2ZfT_yg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Saturday, July 13, 2024, 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/16/transaction-iso.html
> Description:
>
> 'UPDATE, DELETE, MERGE, SELECT FOR UPDATE, and SELECT FOR SHARE commands
> behave the same as SELECT in terms of searching for target rows:
>
> What behavior does the INSERT command exhibit?
>
Inserts don’t search for existing rows.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-07-16 14:20:19 | Re: Mismatch for connection key/value pair between documentation and code? |
| Previous Message | PG Doc comments form | 2024-07-16 09:11:35 | Change detail text in last example of 43.5.3. Executing a Command with a Single-Row Result |