Repository navigation
reload config issue #164
Description
Activity
Hi,
I can reproduce this behavior in my environment.
Commenting out a parameter and reloading does not restore it to its default value.
This is the current behavior.However, this is not the behavior the development team intended, and we're planning to fix it.
As a workaround, either:
- keep the parameter uncommented, set it explicitly to its default value, and reload.
- comment it out and restart Pgpool-II so the default value is applied at startup.
Hi,
I have created a patch to fix this issue.
With this patch, commenting out a parameter in pgpool.conf and reloading Pgpool-II resets the parameter to its default value.
I would appreciate it if you could apply the patch and verify that it works as expected in your environment.Best Regards,
v4-0001-Fix-Reset-removed-config-parameters-to-defaults.patch
- added 6 commits that reference this issue
on Sep 9, 2026
Metadata
Metadata
Assignees
Labels
No labels
hi，
I met an issue ，could you help have a look at it?
reproduce:
log_connections = on# log_connections = on./pgpool -f ../etc/pgpool.conf reload
my concern:
for my understanding, in step 6, the result should be recovered to default value? right?
I checked code, when parent process received reload sig, it will send this sig to all child processes, then child call check_config_reload()->pool_get_config() to reload config file, but it will ignore commented lines in pgpool.conf, so the commented lines would not be recovered to default value.
I'm not quite sure if this is the original design intention.
Thanks a lot!