-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Enahance parsing of postgres configuration booleans in webhooks #4252
Comments
mnencia
changed the title
Enahance parsing of postgres booleans in webhooks
[Feature]: Enahance parsing of postgres configuration booleans in webhooks
Apr 9, 2024
archive_mode is not a boolean but an enum, so this doesn't apply. |
leonardoce
pushed a commit
that referenced
this issue
May 28, 2024
Allows any valid Postgres boolean for configuration in the webhooks. Currently, only `off` and `on` are properly understood by the webhooks. Closes #4252 Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com>
cnpg-bot
pushed a commit
that referenced
this issue
May 28, 2024
Allows any valid Postgres boolean for configuration in the webhooks. Currently, only `off` and `on` are properly understood by the webhooks. Closes #4252 Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com> (cherry picked from commit 9a09548)
cnpg-bot
pushed a commit
that referenced
this issue
May 28, 2024
Allows any valid Postgres boolean for configuration in the webhooks. Currently, only `off` and `on` are properly understood by the webhooks. Closes #4252 Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com> (cherry picked from commit 9a09548)
cnpg-bot
pushed a commit
that referenced
this issue
May 28, 2024
Allows any valid Postgres boolean for configuration in the webhooks. Currently, only `off` and `on` are properly understood by the webhooks. Closes #4252 Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com> (cherry picked from commit 9a09548)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the Postgres docs about the config file:
In webhooks, we compare the
archive_mode
andwal_log_hints
parameter values to "off".That means that a user could set it to "0", "no", or even "OFF" and go ahead with a broken configuration.
Originally posted by @mnencia in #4218 (comment)
The text was updated successfully, but these errors were encountered: