Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit dc6070b

Browse files
committed
Update PG_CACHE_LINE_SIZE description.
PG_CACHE_LINE_SIZE was originally only used in xlog.c, but this hasn't been true for a very long time and is now wildly used, so modify its description to not mention any explicit source code file. Author: Julien Rouhaud Discussion: https://www.postgresql.org/message-id/20230701074936.p3qcssl4t7murt2q@jrouhaud
1 parent 9945750 commit dc6070b

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

src/include/pg_config_manual.h

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -217,13 +217,13 @@
217217
#define DEFAULT_EVENT_SOURCE "PostgreSQL"
218218

219219
/*
220-
* Assumed cache line size. This doesn't affect correctness, but can be used
221-
* for low-level optimizations. Currently, this is used to pad some data
222-
* structures in xlog.c, to ensure that highly-contended fields are on
223-
* different cache lines. Too small a value can hurt performance due to false
224-
* sharing, while the only downside of too large a value is a few bytes of
225-
* wasted memory. The default is 128, which should be large enough for all
226-
* supported platforms.
220+
* Assumed cache line size. This doesn't affect correctness, but can be used
221+
* for low-level optimizations. This is mostly used to pad various data
222+
* structures, to ensure that highly-contended fields are on different cache
223+
* lines. Too small a value can hurt performance due to false sharing, while
224+
* the only downside of too large a value is a few bytes of wasted memory.
225+
* The default is 128, which should be large enough for all supported
226+
* platforms.
227227
*/
228228
#define PG_CACHE_LINE_SIZE 128
229229

0 commit comments

Comments
 (0)