Bump psycopg2-binary from 2.8.5 to 2.9.4

[dependabot]

Bumps psycopg2-binary from 2.8.5 to 2.9.4.

Changelog

Sourced from psycopg2-binary's changelog.

Current release

What's new in psycopg 2.9.4 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Fix ~psycopg2.extras.register_composite(), ~psycopg2.extras.register_range() with customized :sql:search_path (:ticket:[#1487](https://github.com/psycopg/psycopg2/issues/1487)).
• Handle correctly composite types with names or in schemas requiring escape.
• Find pg_service.conf file in the /etc/postgresql-common directory in binary packages (:ticket:[#1365](https://github.com/psycopg/psycopg2/issues/1365)).
• ~psycopg2.errorcodes map and ~psycopg2.errors classes updated to PostgreSQL 15.
• Wheel package compiled against OpenSSL 1.1.1q and PostgreSQL 14.4

What's new in psycopg 2.9.3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Alpine (musl) wheels now available (:ticket:[#1392](https://github.com/psycopg/psycopg2/issues/1392)).
• macOS arm64 (Apple M1) wheels now available (:ticket:1482).

What's new in psycopg 2.9.2 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Raise ValueError for dates >= Y10k (:ticket:[#1307](https://github.com/psycopg/psycopg2/issues/1307)).
• ~psycopg2.errorcodes map and ~psycopg2.errors classes updated to PostgreSQL 14.
• Add preliminary support for Python 3.11 (:tickets:[#1376](https://github.com/psycopg/psycopg2/issues/1376), [#1386](https://github.com/psycopg/psycopg2/issues/1386)).
• Wheel package compiled against OpenSSL 1.1.1l and PostgreSQL 14.1 (:ticket:[#1388](https://github.com/psycopg/psycopg2/issues/1388)).

What's new in psycopg 2.9.1 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Fix regression with named ~psycopg2.sql.Placeholder (:ticket:[#1291](https://github.com/psycopg/psycopg2/issues/1291)).

What's new in psycopg 2.9

• with connection starts a transaction on autocommit transactions too (:ticket:[#941](https://github.com/psycopg/psycopg2/issues/941)).
• Timezones with fractional minutes are supported on Python 3.7 and following (:ticket:[#1272](https://github.com/psycopg/psycopg2/issues/1272)).
• Escape table and column names in ~cursor.copy_from() and ~cursor.copy_to().

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cwegener]

Hi @Samira-El

I saw that pipelinewise-tap-postgres has already been updated to psycopg2-binary 2.9.3

I tested target-postgres against psycopg2-binary 2.9.3 myself and don't have any problems with that.

It would be really good to keep such a critical library as close as up-to-date as possible.

The upstream project (psyscopg2) is making an excellent effort at keeping the OpenSSL security fix releases up-to-date as soon as new OpenSSL releases are available.

And it is concerning that this level of rigor is not applied to pipelinewise-target-postgres as well, when it comes to consuming the security updates provide from upstream in the form of psycopg2-binary security updates. (But for some reason the problem does not exist with pipelinewise-tap-postgres to the same degree)

Hope that makes sense.

Cheers,

Christoph

[dependabot]

Superseded by #106.