From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | radiodiversion <radiodiversion(at)gmail(dot)com> |
Cc: | Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Unclear\mistakable description of UPDATE behaviour in "13.2.1. Read Committed Isolation Level" |
Date: | 2021-08-19 23:47:32 |
Message-ID: | CAKFQuwbGh_=-Tr8_9-kN4kPeGYUGB+HXvDMriXFnAPqK6Y0bsA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Aug 17, 2021 at 11:18 PM radiodiversion <radiodiversion(at)gmail(dot)com>
wrote:
> change sentence: "The search condition of the command (the WHERE clause)
> is re-evaluated to see if the updated version of the row still matches the
> search condition."
>
with sentence: "The search condition of the command (the WHERE clause) is
> re-evaluated only for updated versions of rows to see if they still match
> the search condition. Note that this is different from re-executing the
> command."
>
I'm indifferent about adding the additional note about this not being a new
command start: while the whole of the paragraph makes it clear that once
the command begins it waits and then continues the added note isn't going
to make things worse.
I do not believe the "only for updated versions of rows" is an improvement
- the immediately preceding sentence already says exactly that. I'd rather
use fewer words in this already quite long paragraph.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2021-08-23 15:46:17 | refresh concurrently: limitation of diff refreshing |
Previous Message | Bruce Momjian | 2021-08-18 16:17:03 | Re: ECPG cursor examples should include EXEC SQL WHENEVER NOT FOUND CONTINUE; after the while loop |