Re: Is this a typo?

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Chao Li <li.evan.chao@gmail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2025-11-11T04:45:41Z
Lists: pgsql-hackers
On Tue, Nov 11, 2025 at 4:45 PM Peter Smith <smithpb2250@gmail.com> wrote:
> IMO it's a typo. The correct spelling is "cacheable", so it should be
> corrected where you reported and also in the other two places.

+1

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.

Now can anyone explain why database people write "sargable[1]", but
universally pronounce it as "sargeable"?  That shows the reason to
keep an e around before an a, in our chaotic spelling system, if you
can call it a system :-)

[1] https://en.wikipedia.org/wiki/Sargable



Commits

  1. Prefer spelling "cacheable" over "cachable".