David,
I don't know whether a change along those lines to the configuration
reference page is useful or not - I wouldn't make one without a
comprehensive re-read of the actual background/learning section of the
documentation. My gut instinct is that I just don't think the
documentation can do t
David,
I think part of the issue is your operating with a mental model of
this contrary to the one the documentation was written for.
I made this assumption(checkpoints triggered by size,
checkpoint_completion_target=1) only for simplifying example.
(Although there is a practical task: calcula
David,
For 0.5 you get 2/3rds consumption: ( n / ( 1 + 0.5 ) ) = n * 2/3
Exactly, for checkpoint_completion_target=0.5 the distance between
checkpoints is 2/3 of max_wal_size.
But back to the documentation of max_wal_size.
"Maximum size to let the WAL grow to between automatic WAL checkpoi
David,
This setting is the indirect means to ensure that the WAL directory
doesn't get too large by forcing a checkpoint thus allowing the
corresponding WAL to be removed.
This is a soft limit, ok.
But the question is a little different.
Suppose we have: version >= 11, no replication slots,
