Re: 13.2.1. Read Committed Isolation Level

On Tue, Jul 16, 2024 at 7:06 AM PG Doc comments form wrote: > Or does it mean that contrary to Read > Committed Isolation Level, uncommitted changes from a parallel transaction > can affect the execution of an INSERT command? > This. Because you are keying off of an unique index that has indepe

Re: 13.2.1. Read Committed Isolation Level

On Sun, 2024-07-14 at 06:17 +, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/16/transaction-iso.html > Description: > > I don't understend this text. > > [five paragraphs from the documentation] > > Could you please describe this behavior in more detail? It is difficult

Re: Mismatch for connection key/value pair between documentation and code?

On Monday, July 15, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/libpq-connect.html > Description: > > > For the following document regarding connect string, it is not aligned with > the code.

Re: 13.2.2. Repeatable Read Isolation Level #

On Saturday, July 13, 2024, PG Doc comments form 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

Mismatch for connection key/value pair between documentation and code?

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/libpq-connect.html Description: Hi PostgreSQL documentation team, I have a confusion regarding parameters used in documentation vs. that in the code. Please clarify if I misunderstand

Change detail text in last example of 43.5.3. Executing a Command with a Single-Row Result

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/plpgsql-statements.html Description: The last example in the chapter uses a named parameter "username". As a result, the detail message should use "username" instead of "$1" to match the r

13.2.2. Repeatable Read Isolation Level #

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: they will only f

13.2.1. Read Committed Isolation Level

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/transaction-iso.html Description: I don't understend this text. 'INSERT with an ON CONFLICT DO UPDATE clause behaves similarly. In Read Committed mode, each row proposed for insertion wil