Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump relstorage[postgresql] from 2.1.1 to 3.4.1 #197

Closed

Conversation

dependabot-preview[bot]
Copy link

Bumps relstorage[postgresql] from 2.1.1 to 3.4.1.

Changelog

Sourced from relstorage[postgresql]'s changelog.

3.4.1 (2021-04-12)

  • RelStorage has moved from Travis CI to GitHub Actions for macOS and Linux tests and manylinux wheel building. See 437.
  • RelStorage is now tested with PostgreSQL 13.1. See 427.
  • RelStorage is now tested with PyMySQL 1.0. See 434.
  • Update the bundled boost C++ library from 1.71 to 1.75.
  • Improve the way store connections are managed to make it less likely a "stale" store connection that hasn't actually been checked for liveness gets used.

3.4.0 (2020-10-19)

  • Improve the logging of zodbconvert. The regular minute logging contains more information and takes blob sizes into account, and debug logging is more useful, logging about four times a minute. Some extraneous logging was bumped down to trace.

  • Fix psycopg2 logging debug-level warnings from the PostgreSQL server on transaction commit about not actually being in a transaction. (Sadly this just squashes the warning, it doesn't eliminate the round trip that generates it.)

  • Improve the performance of packing databases, especially history-free databases. See 275.

  • Give zodbpack the ability to check for missing references in RelStorages with the --check-refs-only argument. This will perform a pre-pack with GC, and then report on any objects that would be kept and refer to an object that does not exist. This can be much faster than external scripts such as those provided by zc.zodbdgc, though it definitely only reports missing references one level deep.

    This is new functionality. Feedback, as always, is very welcome!

  • Avoid extra pickling operations of transaction meta data extensions by using the new extension_bytes property introduced in ZODB 5.6. This results in higher-fidelity copies of storages, and may slightly improve the speed of the process too. See 424.

  • Require ZODB 5.6, up from ZODB 5.5. See 424.

  • Make zodbconvert much faster (around 5 times faster) when the destination is a history-free RelStorage and the source supports record_iternext() (like RelStorage and FileStorage do). This also applies to the copyTransactionsFrom method. This is disabled with the --incremental option, however. Be sure to read the updated zodbconvert documentation.

3.3.2 (2020-09-21)

  • Fix an UnboundLocalError in case a store connection could not be opened. This error shadowed the original error opening the connection. See 421.

3.3.1 (2020-09-14)

  • Manylinux wheels: Do not specify the C++ standard to use when compiling. This seemed to result in an incompatibility with manylinux1 systems that was not caught by auditwheel.

3.3.0 (2020-09-14)

  • The "MySQLdb" driver didn't properly use server-side cursors when requested. This would result in unexpected increased memory usage for things like packing and storage iteration.

  • Make RelStorage instances implement IStorageCurrentRecordIteration. This lets both history-preserving and history-free storages work with zodbupdate. See 389.

  • RelStorage instances now pool their storage connection. Depending on the workload and ZODB configuration, this can result in requiring fewer storage connections. See 409 and 417.

    There is a potential semantic change: Under some circumstances, the loadBefore and loadSerial methods could be used to load states from the future (not visible to the storage's load connection) by using the store connection. This ability has been removed.

  • Add support for Python 3.9.

  • Drop support for Python 3.5.

  • Build manylinux x86-64 and macOS wheels on Travis CI as part of the release process. These join the Windows wheels in being automatically uploaded to PyPI.

3.2.1 (2020-08-28)

  • Improve the speed of loading large cache files by reducing the cost of cache validation.

... (truncated)

Commits
  • 4bd8929 Preparing release 3.4.1
  • 426be9f Tell zest.releaser not to create a wheel. CI does that.
  • 5e6ef78 Merge pull request #452 from zodb/better_store_conn_cleanup
  • 825c0aa Improve the way store connections are managed
  • a8f517a Add implementation notes on readCurrent on PostgreSQL: it does disk IO. [skip...
  • 9e7a638 Add in-process contended local_client benchmarks. [skip ci]
  • bf567fc Tweak multiplier in testing locks on CI.
  • 0051e3a Merge pull request #447 from zodb/boost_1_75
  • 405febd Fix links in README.rst [skip ci]
  • 998e3d5 Update bundled boost from 1.71 to 1.75.
  • Additional commits viewable in compare view

Dependabot compatibility score

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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [relstorage[postgresql]](https://github.com/zodb/relstorage) from 2.1.1 to 3.4.1.
- [Release notes](https://github.com/zodb/relstorage/releases)
- [Changelog](https://github.com/zodb/relstorage/blob/master/CHANGES.rst)
- [Commits](zodb/relstorage@2.1.1...3.4.1)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Apr 12, 2021
@dependabot-preview
Copy link
Author

Superseded by #200.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/relstorage-postgresql--3.4.1 branch April 21, 2021 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants