Re: GiST README typos

2025-11-06 Thread John Naylor
On Thu, Nov 6, 2025 at 1:36 PM Paul A Jungwirth wrote: > > On Wed, Nov 5, 2025 at 7:00 PM John Naylor 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-ch

Re: GiST README typos

2025-11-05 Thread Paul A Jungwirth
On Wed, Nov 5, 2025 at 7:00 PM John Naylor 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 a

Re: GiST README typos

2025-11-05 Thread John Naylor
On Wed, Nov 5, 2025 at 1:19 PM Paul A Jungwirth wrote: > Here are fixes to a few typos I found in the GiST README. the child might have migrated as a result of concurrent splits of the -parent, gistFindCorrectParent() is used to find the parent page. +parent, so gistFindCorrectParent() is used t

GiST README typos

2025-11-04 Thread Paul A Jungwirth
Hi Hackers, Here are fixes to a few typos I found in the GiST README. Yours, -- Paul ~{:-) [email protected] v1-0001-Fix-a-few-typos-in-the-GiST-README.patch Description: Binary data