I'm curious to hear why you aren't using the pg native bindings? about fire HOT 3 CLOSED

Hi! I haven't seen an immediate need to implement the native bindings yet. I'm running a couple of projects in production without the native bindings and I have no performance issues whatsoever (as long as indices are configured correctly of course).

They do claim a speed improvement of 20%-30%. This seems worth testing. It looks like it does add an extra dependencies which could make the on-boarding more difficult. I'm actually trying to remove some dependencies, like bower, to ease the on-boarding (have a look at the develop branch).

Would you advise on using the native bindings instead and what do you thinking of the extra dependency?

from fire.

It seems like it's worth testing.

The two main differences in the code are brianc/node-postgres#762 (unconfirmed) and brianc/node-postgres#736 (confirmed).

For the dependency, in order to install pg-native, there first has to be a check/test that runs to confirm that the postgres client and libraries are already installed on the system. The author suggests just checking for pg_config to be in the PATH. We could add this to a preinstall script in npm.

I completely agree on removing dependencies, especially ones like bower or grunt or gulp. I prefer to see 100% use of npm (+package.json scripts), as this keeps the project a lot simpler.

Hope that helps.

from fire.

This issue is not relevant anymore. Please have a look at the new version.

from fire.