-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Postgres Native bindings Segfault when querying with empty buffer #675
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
Conversation
brianc
commented
Nov 11, 2014
what version of pg do you have installed? |
postgres 9.3.5_1 with node-postgres 3.5.0 tries with 3.6.2 |
haha - can you try with pg@4.0.0-beta2 ? You'll also need to |
segfault with pg@3.6.2 tries with 4.0.0-beta2 |
haha thanks @L8D - I will consider this bug to be fixed in both branches either way - but I do appreciate you testing them for me! ❤️ |
Okay so pg@4.0.0-beta2 with pg-native@1.5.0 works perfect other than a new 'NOTICE' message for using IF NOT EXISTS |
OH! Can you show me the query you used to produce the notice message? I need to squash those in the new native bindings but wasn't able to figure out a query which would produce one. The queries seem to be different depending on the config level of the database & the database version. By default libpq spits the notice message to stdout, but I can catch it. |
CREATE TABLE IF NOT EXISTS posts (body TEXT) |
radical. good to know it's fixed in the new version! I'll leave it open cause I'm still gonna support the old version for a while - so I'll try to fix it soon. Thanks so much for your help. 😄 |
I'll be going through all my older stuff to find the other segfaults with the native bindings soon. |
Postgres Native bindings Segfault when querying with empty buffer
Releasing new patch version with the fix right now! |