postgresql_pg_hba: fix file parsing #458
Closed
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
betanummeric
force-pushed
the
fix-pg_hba-parsing
branch
from
2663ea7
to
c56f1e0
Compare
|
@betanummeric hi, if the PR is still relevant or can be closed (as well as that initial one) ? If it is but you have no time now, we can keep it open, NP. |
|
Hi @Andersson007 , I forgot about this PR and I don't really have time to proceed now, sorry. I guess the issue about special chars in the pg_hba.conf remains valid (although I didn't keep track of changes). |
|
@betanummeric hi, sure, no problem, let's close the PR |
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.
fixes #420, replaces #423
This PR is a bugfix for the postgresql_pg_hba module: Lines of the
pg_hba.confcan contain quoted fields which can contain#or an escaped quote (\"). This was not parsed correctly before.