Open msakrejda opened 7 years ago
probably should still error out with ECONNRESET, but maybe not with the call stack.
Yeah, it's kinda weird, since if you don't quit immediately, psql will re-establish the session for you. Also, I can't seem to replicate this anymore, so maybe there's more to this. I'll leave it open in case someone else wants to try to repro...
Ok, I've looked some more into this and I can replicate it somewhat reliably, but I have no idea what's going on. The error handler we've added here doesn't trigger for this error, even though it does trigger correctly if, e.g., I change my PATH to exclude psql
. I don't see where else we might be expected to install an error
event handler, but the message clearly complains about a missing error
handler. Could this be a node issue?
@dickeyxxx or @ransombriggs any ideas?
I think this might be related to #99
Steps to repro:
heroku pg:psql
pg_terminate_backend
(I thinkpg:killall
would also work)\q
. You'll get the following error: