Closed jakubknejzlik closed 8 years ago
Me too
Still happening, very occasionally. I'm switching to 1.10...hope it will help.
I was running 1.09 before
You might want to ask postgres community about that - maybe in #postgresql on freenode? It's a postgres thing & not really related exactly to pg-native.
On Mon, Jan 11, 2016 at 7:00 AM, Jakub Knejzlík notifications@github.com wrote:
I was running 1.09 before
— Reply to this email directly or view it on GitHub https://github.com/brianc/node-pg-native/issues/34#issuecomment-170541521 .
Ah, you are right. I've found this thread also: https://github.com/brianc/node-libpq/issues/28
ouch...i see it's your library too :). Also it's not related only to stored procedures. I'll try my best with community. Thanks
haha woe is me
On Mon, Jan 11, 2016 at 3:40 PM, Jakub Knejzlík notifications@github.com wrote:
ouch...i see it's your library too :)
— Reply to this email directly or view it on GitHub https://github.com/brianc/node-pg-native/issues/34#issuecomment-170699432 .
For anyone else running into this error - make sure that you are calling client.query
after the async callback from client.connect
fires
Does anybody have issues ending with this error
Unable to set non-blocking to true
? I'm running on heroku postgres, everything works fine, but after few days all connections return this message and nothing else than dyno restart helps.I'm not saying it's problem of
pg-native
, just asking if anyone experiencing this problem too. :)