brianc
Breaking changes in PG v6.1.0 appear to break pg-query
I expect it is the change to promise-ifying node-postgres after v5, but upgrading pg from v4.4.0 to v6.1.0 seems to break pg-query. I get no error message but my web page just hangs. After experimenting I have narrowed the fault down to upgrading pg, but since I only access it via pg-query I am reporting the issue here as I suspect that pg-query now no-longer works with the latest version of pg. I have tried changing the connection parameters to the new-style config object, but that doesn't help.
pg-query is massively useful and has saved me a ton of boilerplate. I use pg-query for loads of things from logins to data retrieval as it is so convenient. It would be awesome if it could work with pg v6.x.
Am I correct that it is a mismatch between pg-query and node-postgres and, if so, do you have plans to update pg-query (please!)?
@mappagnosis ,
Did you ever get any reply to this? Did you go back to pg.js? I am having issues both with it trying to find a package called pg.js (not just pg) as will ECONRESET.
