ConnectionPool does not expose connection errors #158
Description
Reported here: Kitura/Swift-Kuery-PostgreSQL#25
I think it would be more user friendly if the ConnectionPool exposed underlying database connection errors to users so they can act upon them.
Currently the only time we expose an issue is where we fail to generate connections upon pool creation.
I don't believe we should fail but we should give users the option to handle errors and choose to fail if that is desirable to them.