C comment: correct use of 64-"byte" cache line size
authorBruce Momjian <[email protected]>
Fri, 4 Sep 2020 17:27:52 +0000 (13:27 -0400)
committerBruce Momjian <[email protected]>
Fri, 4 Sep 2020 17:27:52 +0000 (13:27 -0400)
Reported-by: Kelly Min
Discussion: https://postgr.es/m/CAPSbxatOiQO90LYpSC3+svAU9-sHgDfEP4oFhcEUt_X=DqFA9g@mail.gmail.com

Backpatch-through: 9.5

src/include/storage/buf_internals.h

index ecbcf392bc537a65a9261fda93ffb4a2ff8ed624..a8278f61d0989a68980c938385ad39f05ccf4a1e 100644 (file)
@@ -166,7 +166,7 @@ typedef struct BufferDesc
  * Note that local buffer descriptors aren't forced to be aligned - as there's
  * no concurrent access to those it's unlikely to be beneficial.
  *
- * We use 64bit as the cache line size here, because that's the most common
+ * We use a 64-byte cache line size here, because that's the most common
  * size. Making it bigger would be a waste of memory. Even if running on a
  * platform with either 32 or 128 byte line sizes, it's good to align to
  * boundaries and avoid false sharing.