-
Notifications
You must be signed in to change notification settings - Fork 614
deprecate old code managing sysconfig files #1400
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
deprecate old code managing sysconfig files #1400
Conversation
SimonHoenscheid
commented
Feb 14, 2023
- used on RHEL6
- old Debian and Ubuntu Versions
- Systemd takes care of that now
postgresql::server::config_entry is a typeBreaking changes to this file WILL impact these 6 modules (exact match):Breaking changes to this file MAY impact these 1 modules (near match):postgresql::server::instance::config is a typethat may have no external impact to Forge modules. This module is declared in 70 of 580 indexed public
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we dropped RHEL 6 support in 32b770f (and other EL6 in other commits). If you can confirm the Debian part is no longer relevant then 👍
# we stop the service completely. On RHEL 7 we either have to create | ||
# a systemd override for the port or update the sysconfig file, but this | ||
# is managed for us in postgresql::server::config. | ||
if $facts['os']['name'] == 'Debian' or $facts['os']['name'] == 'Ubuntu' { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no longer relevant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am pretty sure this is no longer needed. And the systemd drop-in is not managed on debian based systems. I would rely on the tests here, but I can also test a bit on a debian based system
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really do wonder how often the data directory is changed. As I mentioned elsewhere, I'm not sure it's supported to have the data directory in postgresql.conf at all. So I think it may be ok to drop. Just a bit unsure about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did this on many debian and ubuntu systems, changing the data directory in postgresql.conf works
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably because they store it in /etc
rather than /var
like Red Hat does (which is crazy).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just verified this on debian 10 with postgresql 11 (debians own package, default), changing port and data directory via postgresql.conf works fine.
* used on RHEL6 * old Debian and Ubuntu Versions * Systemd takes care of that now
a24df18
75bf399
to
a24df18
Compare