1
0
mirror of https://github.com/postgres/postgres.git synced 2025-11-13 16:22:44 +03:00

Prefer spelling "cacheable" over "cachable".

Previously we had both in code and comments.  Keep the more common and
accepted variant.

Author: Chao Li <lic@highgo.com>
Reviewed-by: Peter Smith <smithpb2250@gmail.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/5EBF1771-0566-4D08-9F9B-CDCDEF4BDC98@gmail.com
This commit is contained in:
Thomas Munro
2025-11-12 14:20:49 +13:00
parent fb9bff0454
commit 2421ade663
2 changed files with 3 additions and 3 deletions

View File

@@ -2248,7 +2248,7 @@ heap_insert(Relation relation, HeapTuple tup, CommandId cid,
ReleaseBuffer(vmbuffer); 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 * 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 * the heaptup data structure is all in local memory, not in the shared
* buffer. * buffer.
@@ -2700,7 +2700,7 @@ heap_multi_insert(Relation relation, TupleTableSlot **slots, int ntuples,
CheckForSerializableConflictIn(relation, NULL, InvalidBlockNumber); 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, * 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 * because the heaptuples data structure is all in local memory, not in
* the shared buffer. * the shared buffer.

View File

@@ -829,7 +829,7 @@ ResetCatalogCachesExt(bool debug_discard)
* kinds of trouble if a cache flush occurs while loading cache entries. * 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, * 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 * 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 void
CatalogCacheFlushCatalog(Oid catId) CatalogCacheFlushCatalog(Oid catId)