Re: GiST README typos - Mailing list pgsql-hackers

From Paul A Jungwirth
Subject Re: GiST README typos
Date
Msg-id CA+renyUiHkzvU48_K+9jMQkzN4Bx0uVv3skxKs9niB7+SENZ9Q@mail.gmail.com
Whole thread Raw
In response to Re: GiST README typos  (John Naylor <johncnaylorls@gmail.com>)
Responses Re: GiST README typos
List pgsql-hackers
On Wed, Nov 5, 2025 at 7:00 PM John Naylor <johncnaylorls@gmail.com> wrote:
>
>  being empty. Whenever we find one, we acquire a lock on the parent and child
> -page, re-check that the child page is still empty. Then, we remove the
> +page, then re-check that the child page is still empty. Then, we remove the
>  downlink and mark the child as deleted, and release the locks.
>
> I still find this a bit awkward -- perhaps "and re-check"? The last
> sentence could do with just the last "and" as well, I think, but
> that's a style consideration and not a grammar fix.

I nearly wrote it that way myself. It's nice that it avoids the double
"then". So I agree, let's go with "and re-check".

Thanks for the review!

Yours,

--
Paul              ~{:-)
pj@illuminatedcomputing.com



pgsql-hackers by date:

Previous
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Assertion failure in SnapBuildInitialSnapshot()
Next
From: jian he
Date:
Subject: Re: inconsistent tableoid handling in COPY WHERE clause