-
Notifications
You must be signed in to change notification settings - Fork 1
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
pgpool-II and node.JS #1
Comments
I have yet to be able to do it. We ended up just going with node-pg built in connection pooling, however we have upgraded to postgres 9.3 and pgpool 3.3.0 and plan on retesting. I'll let you know once I have results. |
Thanks! Was it the parameterized query issue that blocked you or was it something else? Which pgpool version did you use then? |
It was the parametrized queries. We were using 3.1.2. |
Also it looks like in the latest pull from master that it has some changes around parameterized queries. |
I just updated the repo to match the original, so you might want to pull the latest, build and then retest |
Thanks, I have used pgpool 3.3.2 and there is still the same issue. Some threads indicate a regression on that version on a similar issue so I am now checking pgpool 3.3.1. If that will fail then I'm not sure both libraries are interoperable today. |
Good news - downgrading pg-pool from 3.3.2. to 3.3.1 seem to work well with parameterized queries. Doing more testing now. |
Have you guys tested this with 3.3.3? I'd also love to get more details on the parameterized query problem you guys are talking about. I want to use pgpool with Bookshelf (uses knex, which uses pg internally). |
Not yet Sent from the trunk of an El Camino
|
We use pgpool-3.3.3 with Node.JS and parameterized queries work well. |
Hi
Were you able to consume pgpool-II with the 'pg' module in Node.JS? I'm really struggling with those parameterized queries and would be great to hear if it is doable.
Thanks,
Yaron
The text was updated successfully, but these errors were encountered: