Re: Is this a typo?

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is this a typo?
Date: 2025-11-11 05:26:46
Message-ID: CAEoWx2=Fe+HTQQ_AwBJV=V2ZHb_vHbGazbo9zQPz3wrPwsB4qA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 11, 2025 at 12:59 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > I think the incorrect spelling fits the usual pattern (movable,
> > valuable, believable, ... with moveable accepted but dying), and it's
> > definitely "caching" without the -e-, so it's probably a tempting
> > mistake to make, but apparently we're making new words out of bits of
> > French with the C preprocessor ## operator and ignoring all that. I
> > bet it's "cachable" en français though. My Oxford Concise lists only
> > the -e- form, so you have my vote. The online Merriam-Webster (I
> > think that's the main reference for US spelling?) doesn't list either
> > and suggests I might be looking for cashable.
>
> I tend to look to OneLook Dictionary Search:
>
> https://www.onelook.com
>
> Their set of dictionaries has multiple entries for "cacheable"
> and only one for "cachable". I don't agree that the latter is
> wrong exactly, because some people evidently use it and English
> has no Académie Française to legislate what is right; but it's
> clearly the less common spelling.
>
> regards, tom lane
>

Thanks all for the clarification. Peter and Thomas expressed clear
preference for "cacheable", and Tom confirmed it is the more common
spelling. I just created a patch to replace all three occurrences
accordingly.

Best regards,
Chao Li (Evan)
---------------------
HighGo Software Co., Ltd.
https://www.highgo.com/

Attachment Content-Type Size
v1-0001-Changes-cachable-to-cacheable.patch application/octet-stream 2.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-11-11 05:43:01 Re: Make PQgetResult() not return NULL on out-of-memory error
Previous Message Fujii Masao 2025-11-11 05:20:45 Re: Make PQgetResult() not return NULL on out-of-memory error