Skip to content

Conversation

@dimitri
Copy link
Owner

@dimitri dimitri commented Apr 28, 2023

This allows to later review how the command was run, and more importantly editing the configuration file (via new commands, not implemented yet) and signal the already running pgcopydb to dynamically apply new settings.

See #224

@dimitri dimitri force-pushed the feature/config-file branch from 72f86b6 to 9b0e098 Compare May 2, 2023 14:38
dimitri added 3 commits May 12, 2023 11:02
This allows to later review how the command was run, and more importantly
editing the configuration file (via new commands, not implemented yet) and
signal the already running pgcopydb to dynamically apply new settings.
Those commands only work when the config.ini file can be found on-disk,
which is to say when a pgcopydb command has been started already. The
commands allow to review and edit the current settings being used.

At the moment editing the values still has no impact on the running
processes.
The configuration is written to file and can be edited with the new command
pgcopydb config set; now this command also signals the running process with
SIGHUP and the config file can be read and applied on-the-fly.
@dimitri dimitri force-pushed the feature/config-file branch from 9b0e098 to 5942b10 Compare May 12, 2023 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants