Upgrade pg to version 1.4.0

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ pg (~> 0.17 → ~> 1.4) · Repo · Changelog

Release Notes

1.4.0 (from changelog)

Added:

• Add PG::Connection#hostaddr, present since PostgreSQL-12. #453

• Add PG::Connection.conninfo_parse to wrap PQconninfoParse. #453

Bugfixes:

• Try IPv6 and IPv4 addresses, if DNS resolves to both. #452

• Re-add block-call semantics to PG::Connection.new accidently removed in pg-1.3.0. #454

• Handle client error after all data consumed in #copy_data for output. #455

• Avoid spurious keyword argument warning on Ruby 2.7. #456

• Change connection setup to respect connect_timeout parameter. #459

• Fix indefinite hang in case of connection error on Windows #458

• Set connection attribute of PG::Error in various places where it was missing. #461

• Fix transaction leak on early break/return. #463

• Update Windows fat binary gem to OpenSSL-1.1.1o and PostgreSQL-14.4.

Enhancements:

• Don't flush at each put_copy_data call, but flush at get_result. #462

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 44 commits:

• Update to postgresql-14.4 and openssl 1.1.1o for Windows binaries
• Merge pull request #464 from larskanis/bump-1.4.0
• Bump VERSION to 1.4.0
• Add a proxy to enable or disable TCP data flow
• Don't fail at GC.compact spec on ppc64le
• Avoid compiler warnings
• Remove unnecessary variable assignments
• Merge pull request #463 from ejoubaud/fix-transaction-leak
• Remove useless assignments in test
• Fix transaction leak on early break/return
• Revert "April is coming!"
• Set connection attribute of PG::Error
• Avoid old style K&R declaration syntax
• Merge pull request #462 from larskanis/flush
• Don't flush at each put_copy_data call, but flush at get_result
• Remove out-commented debug outputs
• Bundle all conn.copy_data related specs together
• Merge pull request #459 from larskanis/timeout
• Small fix in comment at conn.flush
• Move specs to "OS thread support" into async file
• Fix compat with ruby-2.x
• Move specs which are intended for async context only into a separate file
• Add a test to verify hostnames that resolve to both IPv4 and 6
• Adjust spec for connect_timeout to pass on older Postgres servers
• Fix compat with Windows
• Fix compat with Truffleruby
• Exclude spec using hostaddr at older Servers
• Remove debug output
• Adjust method documentation
• Fix parse_connect_args specs reg. changes due to connect_timeout
• Merge specs of removed PG::Connection#connect_string_to_hash to conninfo_parse
• Change connection setup to respect connect_timeout parameter
• Change connection setup to respect connect_timeout parameter
• Add specs to PG::Connection.conninfo_parse
• Add conn.conninfo_parse to wrap PQconninfoParse
• Improve API documentation to conn.host
• Add PG::Connection#hostaddr
• Add a useful example to conn.status
• Merge pull request #456 from jeremyevans/avoid-ruby27-keyword-warning
• Avoid spurious keyword argument warning on Ruby 2.7
• Add block-call semantics to PG::Connection.new
• Merge pull request #455 from stevewoodcock/ignore-get-copy-data-error
• Fix for TruffleRuby, raise original exception explicitly
• Handle client error after all data consumed in #copy_data for output

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #15.