Skip to content
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

Let listen_addresses be defined independently #865

Merged
merged 1 commit into from May 25, 2017

Conversation

hasegeli
Copy link
Contributor

Postgresql module is often extended by other shared modules. Shared modules should not use resource-like class definitions to let the callers use them when necessary. It is still a reasonable behaviour for the shared module to set max_connections. Making it optional would allow this to happen.

Removing the default value "localhost" should not break anything as it is already the default of PostgreSQL and on every distribution I know of.

@hunner hunner merged commit d7a0771 into puppetlabs:master May 25, 2017
hunner added a commit that referenced this pull request May 25, 2017
Postgresql module is often extended by other shared modules.  Shared modules should not use resource-like class definitions to let the callers use them when necessary.  It is still a reasonable behaviour for the shared module to set max_connections.  Making it optional would allow this to happen.

Removing the default value "localhost" should not break anything as it is already the default of PostgreSQL and on every distribution I know of.
@hunner
Copy link
Contributor

hunner commented May 25, 2017

Of note, if the listen_address is not configured at all then postgresql will only create a unix socket. If it is present, it will create a tcp socket as well. That makes this change backwards-incompatible.

@hasegeli
Copy link
Contributor Author

hasegeli commented May 25, 2017 via email

cegeka-jenkins pushed a commit to cegeka/puppet-postgresql that referenced this pull request Feb 3, 2022
Postgresql module is often extended by other shared modules.  Shared modules should not use resource-like class definitions to let the callers use them when necessary.  It is still a reasonable behaviour for the shared module to set max_connections.  Making it optional would allow this to happen.

Removing the default value "localhost" should not break anything as it is already the default of PostgreSQL and on every distribution I know of.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants