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

Cannot parse string: COMMENT ON COLUMN #260

Open
garykuipers opened this issue Sep 23, 2019 · 6 comments
Open

Cannot parse string: COMMENT ON COLUMN #260

garykuipers opened this issue Sep 23, 2019 · 6 comments

Comments

@garykuipers
Copy link

Apparently, form a comment in August 2018:

Postgres changed the way that search path semantics are used in pg_dump in response to this:
https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path

The affect took place earlier this year (March 2018) and affects all supported versions of postgres/pg_dump.

This affects all users of apgdiff, so it would be good to see a fix to address it.

@jalissonmello
Copy link
Contributor

Already exists a PR with the fix. #257

@garykuipers
Copy link
Author

garykuipers commented Sep 24, 2019 via email

@jalissonmello
Copy link
Contributor

The possible fix it's waiting for maintainers review and need to be merged in the main branch.
I you want to test, need to compile yourself the project and include the fix

@garykuipers
Copy link
Author

garykuipers commented Sep 25, 2019 via email

@d1maxa
Copy link

d1maxa commented Oct 25, 2019

I fixed one more error during parsing comments yesterday, you can try my fork version

@garykuipers
Copy link
Author

garykuipers commented Oct 25, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants