From 2421ade663e96e7245e6bbf960b0f6861e39e455 Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Wed, 12 Nov 2025 14:20:49 +1300 Subject: [PATCH] Prefer spelling "cacheable" over "cachable". Previously we had both in code and comments. Keep the more common and accepted variant. Author: Chao Li Reviewed-by: Peter Smith Reviewed-by: Tom Lane Discussion: https://postgr.es/m/5EBF1771-0566-4D08-9F9B-CDCDEF4BDC98@gmail.com --- src/backend/access/heap/heapam.c | 4 ++-- src/backend/utils/cache/catcache.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index 36fee9c994e..4b0c49f4bb0 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -2248,7 +2248,7 @@ heap_insert(Relation relation, HeapTuple tup, CommandId cid, ReleaseBuffer(vmbuffer); /* - * If tuple is cachable, mark it for invalidation from the caches in case + * If tuple is cacheable, mark it for invalidation from the caches in case * we abort. Note it is OK to do this after releasing the buffer, because * the heaptup data structure is all in local memory, not in the shared * buffer. @@ -2700,7 +2700,7 @@ heap_multi_insert(Relation relation, TupleTableSlot **slots, int ntuples, CheckForSerializableConflictIn(relation, NULL, InvalidBlockNumber); /* - * If tuples are cachable, mark them for invalidation from the caches in + * If tuples are cacheable, mark them for invalidation from the caches in * case we abort. Note it is OK to do this after releasing the buffer, * because the heaptuples data structure is all in local memory, not in * the shared buffer. diff --git a/src/backend/utils/cache/catcache.c b/src/backend/utils/cache/catcache.c index 30ac1bd91be..b6408d46e2b 100644 --- a/src/backend/utils/cache/catcache.c +++ b/src/backend/utils/cache/catcache.c @@ -829,7 +829,7 @@ ResetCatalogCachesExt(bool debug_discard) * kinds of trouble if a cache flush occurs while loading cache entries. * We now avoid the need to do it by copying cc_tupdesc out of the relcache, * rather than relying on the relcache to keep a tupdesc for us. Of course - * this assumes the tupdesc of a cachable system table will not change...) + * this assumes the tupdesc of a cacheable system table will not change...) */ void CatalogCacheFlushCatalog(Oid catId) -- 2.39.5