The test errors seem to result from the same source as in django: lcd1232/django-postgrespool2#11. The issue is described in a PR to the same repository lcd1232/django-postgrespool2#12. Trying to find out where to insert the same fix: https://github.com/lcd1232/django-postgrespool2/pull/12/files#diff-81ec40a918dd202e487e160513255b32R56

We won't backport the requirement as it's too risky, but we will mention it on the CHANGELOG.
We will backport the small code change related to the connection property, which should be able to handle both versions of psycopg2 (via some AttributeError catching or similar)

Does this make sense @bzar ?

Yes, that makes sense. There's no telling what other non obvious side effects the upgrade has and it shouldn't for now be done unless it's necessary. The compatibility fix should work either way.

Added just the code change in 2.8 as agreed (f9aaf91). Apparently the new syntax (3 connection) is compatible with the psycopg2 version used in CKAN 2.8 (2.7.3.2), probably because the second connection is just a pool, but to be safe I added an AttributeError check.

Hi, when to release a new 2.8.x version to use psycopg2 2.8.4?

Also, requests version upgrade, and in datapusher.

Regards

Note that for backporting as far back as 2.6 psycopg2==2.7.7 works for postgres 10 and the updated ssl libraries (e.g. on travis) but also prevents this error that happens with psycopg2==2.8.2

  File "/usr/lib/ckan/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 435, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.DBAPIError: (UndefinedTable) relation "user" does not exist
LINE 2: FROM "user"
...