diff options
| author | Michael Paquier <michael@paquier.xyz> | 2023-01-19 13:13:30 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2023-01-19 13:13:30 +0900 |
| commit | fed4e92f3bfd4dfbbee472fb4b0b86d9b9100a3c (patch) | |
| tree | f77b53e0f33749571fcd520e83b5d69b0842be0a /src | |
| parent | dfe96d6130694e43bf078de0c9e39b55bc222b7a (diff) | |
| download | postgresql-fed4e92f3bfd4dfbbee472fb4b0b86d9b9100a3c.tar.gz postgresql-fed4e92f3bfd4dfbbee472fb4b0b86d9b9100a3c.zip | |
Add missing assign hook for GUC checkpoint_completion_target
This is wrong since 88e9823, that has switched the WAL sizing
configuration from checkpoint_segments to min_wal_size and
max_wal_size. This missed the recalculation of the internal value of
the internal "CheckPointSegments", that works as a mapping of the old
GUC checkpoint_segments, on reload, for example, and it controls the
timing of checkpoints depending on the volume of WAL generated.
Most users tend to leave checkpoint_completion_target at 0.9 to smooth
the I/O workload, which is why I guess this has gone unnoticed for so
long, still it can be useful to tweak and reload the value dynamically
in some cases to control the timing of checkpoints.
Author: Bharath Rupireddy
Discussion: https://postgr.es/m/CALj2ACXgPPAm28mruojSBno+F_=9cTOOxHAywu_dfZPeBdybQw@mail.gmail.com
Backpatch-through: 11
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/utils/misc/guc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c index 3acafaad5a8..98651b473a9 100644 --- a/src/backend/utils/misc/guc.c +++ b/src/backend/utils/misc/guc.c @@ -3638,7 +3638,7 @@ static struct config_real ConfigureNamesReal[] = }, &CheckPointCompletionTarget, 0.5, 0.0, 1.0, - NULL, NULL, NULL + NULL, assign_checkpoint_completion_target, NULL }, { |