Re: [PATCH} Move instrumentation structs

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Mario González Troncoso <gonzalemario(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH} Move instrumentation structs
Date: 2026-01-12 20:24:43
Message-ID: CAApHDvqPmpa53jcTmfU8arFFm7=hB5cFoXX5dcUH=1qV0tRFHA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 6 Jan 2026 at 03:39, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> I also happened to notice an old typo "its" which should be "it's" in
> tuplesort.c while reading your patch.

There's a bit of conflicting opinion going on here with the changes
made in 128897b101e0.

"false when it's value for in-memory space"

I think the differing opinions depend on what you fill in the missing
words with in the badly written English. If you read "value" as "the
value", then "it's" is correct. Whereas if you read it as "value is",
then "its" is correct. I assume you didn't read it the same way as
John did.

Maybe worth fixing this up to prevent this from being continually
changed and changed back.

How about:

- bool isMaxSpaceDisk; /* true when maxSpace is value
for on-disk
- *
space, false when it's value for in-memory
- * space */
+ bool isMaxSpaceDisk; /* true when the maxSpace
value tracking is
+ *
on-disk space, false means it's tracking
+ *
memory space */

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-01-12 21:54:34 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Mihail Nikalayeu 2026-01-12 18:54:56 Re: Adding REPACK [concurrently]