Version 2.0

[brianc]

Upgrading to support multiple result-sets returned from a multi-command simple query.

Example:

client.query('SELECT 1 as num; SELECT 2 as othernum;', (err, rows) => {
  // pg-native @ 1.x rows == [{ num: 1 }, { othernum: 2 }]
  // pg-native @ 2.x rows == [[ { num: 1 } ], [ { othernum: 2 }]]
})

That is a breaking change though relying on the old behavior was never really a good idea as you had no indication of which row came from which result-set.

Everything else should behave as it did before.

Additions:

• Added result as a 2nd succes parameter to query callbacks. This more closely mimics node-postgres query result behavior and gives introspection into the fields returned with the query. This further helps disambiguate between multi-result-set columns.
• Substnatially refactored internals, increasing speed.
• Fixed bug which could make libpq cause the run-loop to block in certain multiple, large response reading scenarios or when a lot of errors were happening at once.