Tune notification spooling #558
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Raise the number of maximum connections for default PostgreSQL, so it could act as the server for integration testing, even with very little resources in the small instance type we're using. Also enable IAM authentication, as that seems to be the default, just in case setting our own flags overrides it (no time for testing, sorry).
Revoke the default permission to create object in the public schema of each KCIDB database in PostgreSQL. That permission is granted per-user, and the default was overlooked until recently.
Reduce the instances of notification-spooling Cloud Functions to just two to reduce the load on PostgreSQL, and double their memory, as they're hitting the current limit quite often now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reduce the instances of notification-spooling Cloud Functions to just two to reduce the load on PostgreSQL, and double their memory, as they're hitting the current limit quite often now.
Revoke the default permission to create object in the public schema of each KCIDB database in PostgreSQL. That permission is granted per-user, and the default was overlooked until recently.
Supply the currently-used PostgreSQL instance settings when creating, so we don't lose them.