-
Notifications
You must be signed in to change notification settings - Fork 28
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
ecpg error on new lines #18
Comments
Can you provide a sql file that reproduces the problem? |
@markdrago
|
I tried reproducing this and, as you said, it works in python 3.5.2. It also works with python 2.7.12. To be honest, I'm tempted to not make any changes. While I can't back it up, I think the munmap_chunk error is more indicative of a problem in ecpg than in pgsanity. I'd rather not work around it - especially if it works in the latest versions of python2 and python3. Is it possible that your two tests are using different versions of ecpg as well? Was the python 3.4.3 test and the 3.5.2 test executed on the same machine with the same ecpg? |
@markdrago yes, you are right:
and with:
I did not get the error.
any how I'm good... @markdrago thanks for your replay |
tldr; check your |
I'm running the same version of ecpg that gave you a problem:
I think we'll just hold tight for now and see if anyone else is able to reproduce. |
on running:
with a multi-line sql command I get:
*** Error in `ecpg': munmap_chunk(): invalid pointer: ***
I have found a workaround:
meaning I remove all empty lines.
I tried adding this snippet in:
pgsanity.pgsanity.ecpg.check_syntax
but it broke the tests:how can I fix this?
The text was updated successfully, but these errors were encountered: