diff options
| author | Michael Paquier <michael@paquier.xyz> | 2023-01-19 13:13:27 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2023-01-19 13:13:27 +0900 |
| commit | 49e3a5e7149d3f676318f2222aaab30613f8dc59 (patch) | |
| tree | daf79be7fb1b38ba4a48c0038f990e9b6ba03441 /src/backend/utils/adt/jsonb_util.c | |
| parent | 1391916736cf218c7f234471ef3c98f740ed2a5e (diff) | |
| download | postgresql-49e3a5e7149d3f676318f2222aaab30613f8dc59.tar.gz postgresql-49e3a5e7149d3f676318f2222aaab30613f8dc59.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/backend/utils/adt/jsonb_util.c')
0 files changed, 0 insertions, 0 deletions