Skip to content
Snippets Groups Projects
  1. Nov 02, 2017
  2. Nov 01, 2017
  3. Oct 26, 2017
  4. Oct 24, 2017
  5. Sep 27, 2017
  6. Dec 28, 2016
  7. Oct 25, 2016
  8. Aug 29, 2016
  9. Jul 01, 2016
    • Gavin M. Roy's avatar
      Bump the version · ff7e2043
      Gavin M. Roy authored
    • Gavin M. Roy's avatar
      Be more explicit in exception catching · 6b9a5404
      Gavin M. Roy authored
      - Instead of catchig a bare exception, catch the two known exception types that could be thrown when adding a connection to a pool.
      - Increase logging usefulness
      - Don't resue the results variable that is used as an import for queries.results
      6b9a5404
    • Gavin M. Roy's avatar
      Increase logging usefulness · 164e58e5
      Gavin M. Roy authored
      164e58e5
    • Gavin M. Roy's avatar
      Address possible race condition · 7f994b57
      Gavin M. Roy authored
      - If too many simultaneous new connections are being made at the same time, it is possible that a pool can fill up by the time a connection is finally established when used asynchronously. This could cause leaked psycopg2 connections to occur when the PoolFullError is raised. To address this, the connection is closed prior to the error being raised. In addition, when closing the connection, make sure that if for any reason psycopg2 raises an exception, we handle that.
      - Update all Queries exceptions to use a base QueriesException to they're easier to catch at a level that's isolated to the queries package.
      7f994b57
  10. Jun 15, 2016
Loading