Remove invalid temp_file_size line in customPostgresql.conf
#192
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
dessalines
approved these changes
Oct 17, 2023
usr3
pushed a commit
to usr3/futurology-lemmy
that referenced
this pull request
Dec 23, 2023
snowe2010
pushed a commit
to programming-dot-dev/lemmy-ansible
that referenced
this pull request
Jan 30, 2024
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.
Now that customPostgresql.conf is being correctly used, it looks like it has an invalid value which causes PostgreSQL not to start (#191). This PR removes the offending line which allows PostgreSQL to start.
@dessalines @Nutomic If you know what you were using this line for and or what it can be replaced with, let me know.