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 1lqAFs-0002Rl-I4 for pgsql-docs@arkaria.postgresql.org; Mon, 07 Jun 2021 08:05:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lqAFr-0007R0-50 for pgsql-docs@arkaria.postgresql.org; Mon, 07 Jun 2021 08:05:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lpUdO-0000Xt-Q5 for pgsql-docs@lists.postgresql.org; Sat, 05 Jun 2021 11:38:34 +0000 Received: from mail-pg1-x52c.google.com ([2607:f8b0:4864:20::52c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lpUdL-0000Gf-2q for pgsql-docs@lists.postgresql.org; Sat, 05 Jun 2021 11:38:33 +0000 Received: by mail-pg1-x52c.google.com with SMTP id v14so9932452pgi.6 for ; Sat, 05 Jun 2021 04:38:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A+3MZKvnV33O3NL6dEdqGyVLnaA1lBt+f5l9UgKOgnE=; b=F0xgSKBRGwbr0RTadPDa7C8B9CO9MP8tdhV+iVX1AlSP5FHwaRRCt/YQv8NKcuOHls FMThrqQzZpNN7F7sbSXSXiwpwf0bQImqRYu03RWDdoyGUI0Uu0RpN/iy7D+brcAdQcMu +6Pwnc+Lt1skQ2fHIYWshY4MFWA4dnrZqWA+DPEU5ckQtOsLeMb4NMUAGtBtvSjc7lmk iJyX9I0MW0IxebSHdIDHpyQo70pCnLYmWncnhqssFcwoR6RATA1eK4wkt1yrOJE7XhxX T6zs1gTEP0MS1wyA3j8XHHpZygbpTw0gXxCbof2YyWXw9GmQbC743oRpfKhx7n63wQwI eAzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A+3MZKvnV33O3NL6dEdqGyVLnaA1lBt+f5l9UgKOgnE=; b=MfpDMpRNnqCnc/ROEvm8Wxt0nwLyWp7guPfOetOvntR7u5UXjN7EiawQiX061iqyYU aI821bFx1baslPrzAJIwg916uelL5xJrvp/5ofeaL+pti50jBlDs0n9k1raqoSHuh+MH wg7OEKzYhShwdojdnuUOjZr4PZ97bnmoXQk8Lk9SoUNkb6iEAKDfY5B56VLnBDr10eg8 GmmrqH/LuTeC9QI1+TEANnR2sRqKFMzMI+VxJXLax3ndisEBcIUbKES06DNhegIAv4Rx p9a0sFmMU7qWDTXAUwUqpR/ayH9vaUOYOsXuPPiIs0UHGt7XJcG5BnNgxpE5wjGBoeTP +L6A== X-Gm-Message-State: AOAM5332MIqgxDbLmR1geI+dLNzFNqFvw5UMseb9RjcBpw25gWYX32gn gpFmU86FeNFtO8QCtxWnBnbfKRorttrWIrxZprg= X-Google-Smtp-Source: ABdhPJyjHYDTHP2eCx/1PIUVrV4vUe/gWa9qNAxeiXUGgSMXlREHCtzRpiFVB0YULTBk6a/usroU2e7EOJJD2KnZvL0= X-Received: by 2002:aa7:8c02:0:b029:2e9:c513:1e10 with SMTP id c2-20020aa78c020000b02902e9c5131e10mr9194325pfd.2.1622893110149; Sat, 05 Jun 2021 04:38:30 -0700 (PDT) MIME-Version: 1.0 References: <162283882930.14468.5063555039238144271@wrigleys.postgresql.org> <507137.1622852350@sss.pgh.pa.us> In-Reply-To: <507137.1622852350@sss.pgh.pa.us> From: Eric Mutta Date: Sat, 5 Jun 2021 14:37:56 +0300 Message-ID: Subject: Re: Typo in "13.2.3. Serializable Isolation Level" To: Tom Lane Cc: pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000056c66c05c4033f6d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000056c66c05c4033f6d Content-Type: text/plain; charset="UTF-8" > That sentence is a suggestion of an action for the reader to take, conditionally upon verifying that such things are no longer necessary. I see, that makes sense now, I was parsing the sentence differently. Perhaps for clarity those explicit locks could be mentioned in brackets so the sentence reads: > "Eliminate explicit locks (SELECT FOR UPDATE and SELECT FOR SHARE) where no longer needed due to the protections automatically provided by Serializable transactions." That way, the intent of "where no longer needed" being a conditional suggestion is closely connected to the "eliminate explicit locks" instruction. Essentially without the bracketed part it would read: > "Eliminate explicit locks...where no longer needed..." I believe adding brackets would help but in any case, it's not a big deal and I extend my thanks to all the people working on the Postgres docs (as a new user adopting Postgres for my next take-over-the-world project, the comprehensive docs are pure gold!). Many thanks, Eric Mutta. On Sat, Jun 5, 2021 at 3:19 AM Tom Lane wrote: > PG Doc comments form writes: > > The following sentence: > > >> Eliminate explicit locks, SELECT FOR UPDATE, and SELECT FOR SHARE where > no > > longer needed due... > > > Uses the word "where" when it should probably use the word "are" and thus > > read: > > > Eliminate explicit locks, SELECT FOR UPDATE, and SELECT FOR SHARE are no > > longer needed due... > > Hmm, I don't think so. That sentence is a suggestion of an action > for the reader to take, conditionally upon verifying that such things > are no longer necessary. Your wording would turn it into an assertion > that no such things are necessary anywhere. That seems (a) probably > wrong and (b) not grammatically consistent with the other entries in > that bullet list. > > regards, tom lane > --00000000000056c66c05c4033f6d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> That sentence is a suggestion of an = action for the reader to take, conditionally upon verifying that such thing= s are no longer necessary.

I see, that= makes sense now, I was parsing the sentence differently. Perhaps for clari= ty those explicit locks could be mentioned in brackets so the sentence read= s:

> "Eliminate explicit locks (SELECT FOR= UPDATE and SELECT FOR SHARE) where no longer needed due to the protections= automatically provided by Serializable transactions."
<= br>
That way, the intent of "where no longer needed" be= ing a conditional suggestion is closely connected to the "eliminate ex= plicit locks" instruction. Essentially without the bracketed part it w= ould read:

=C2=A0 > "Eliminate explicit lo= cks...where no longer needed..."=C2=A0

I = believe adding brackets would help but in any case, it's not a big deal= and I extend my thanks to all the people working on the Postgres docs (as = a new user adopting Postgres for my next=C2=A0take-over-the-world project, = the comprehensive docs are pure gold!).

Many thank= s,
Eric Mutta.
=C2=A0=C2=A0
On Sat, Jun 5, 2021 at = 3:19 AM Tom Lane <tgl@sss.pgh.pa.us= > wrote:
= PG Doc comments form <noreply@postgresql.org> writes:
> The following sentence:

>> Eliminate explicit locks, SELECT FOR UPDATE, and SELECT FOR SHARE = where no
> longer needed due...

> Uses the word "where" when it should probably use the word &= quot;are" and thus
> read:

> Eliminate explicit locks, SELECT FOR UPDATE, and SELECT FOR SHARE are = no
> longer needed due...

Hmm, I don't think so.=C2=A0 That sentence is a suggestion of an action=
for the reader to take, conditionally upon verifying that such things
are no longer necessary.=C2=A0 Your wording would turn it into an assertion=
that no such things are necessary anywhere.=C2=A0 That seems (a) probably wrong and (b) not grammatically consistent with the other entries in
that bullet list.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane
--00000000000056c66c05c4033f6d--