From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: typo fix |
Date: | 2018-11-20 07:31:33 |
Message-ID: | 176763d9-c921-af42-d713-4eb16a506aa9@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018/11/20 15:58, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>> On Tue, Nov 20, 2018 at 02:00:39PM +0900, Amit Langote wrote:
>>> - * We also use EquivalenceClasses as the base structure for PathKeys, letting
>>> + * We also use EquivalenceClass as the base structure for PathKeys, letting
>
>> ... But not that.
>
> The reason that's not good is that it creates a singular-plural mismatch.
Hmm, yeah.
> If you'd also changed "PathKeys" to "PathKey", it would still read OK,
> though I don't think it's an improvement particularly.
So,
- * We also use EquivalenceClasses as the base structure for PathKeys,
+ * We also use EquivalenceClass as the base structure for PathKey,
> (Hm ... though arguably, "structure" should be "structures" if we're
> going to let it stand as plural.)
vs.
- * We also use EquivalenceClasses as the base structure for PathKeys,
+ * We also use EquivalenceClasses as the base structures for PathKeys,
If I'm understanding this right, aren't different orderings represented by
different PathKey nodes considered equivalent if they share the base
EquivalenceClass? If that's the case, I think the former reads better.
Thanks,
Amit
Attachment | Content-Type | Size |
---|---|---|
EquivalenceClass-typo-v2.patch | text/plain | 1010 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-11-20 07:47:54 | Re: Regarding performance regression on specific query |
Previous Message | Darafei Komяpa Praliaskouski | 2018-11-20 07:23:25 | Re: zheap: a new storage format for PostgreSQL |