Add prepared_statements to database.yml #1994
Merged
Conversation
This file contains hidden or 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
Contributor
Author
|
Is there anything I can do for this patch? |
sue445
force-pushed
the
db_pgbouncer_config
branch
from
983c335 to
9cbdb3e
Compare
sue445
changed the title
solidnerd
requested changes
Sep 24, 2019
Collaborator
solidnerd
left a comment
solidnerd
left a comment
There was a problem hiding this comment.
Thanks for your PR. Could you check my commented changes ?
Co-Authored-By: Niclas Mietz <github@mietz.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I want to use
docker-gitlabwith PgBouncer.But need to disable
prepared_statementsc.f.
So I allowed pass this parameter to
database.yml