Changes in version 3.34.1:
Fix a potential use-after-free bug when processing a a subquery with both a correlated WHERE clause and a "HAVING 0" clause and where the parent query is an aggregate.
Fix documentation typos
Fix minor problems in extensions.
1.3.22
oracle
[oracle] [bug]
Fixed regression which occured due to 5755 which implemented isolation level support for Oracle. It has been reported that many Oracle accounts don’t actually have permission to query the v$transaction view so this feature has been altered to gracefully fallback when it fails upon database connect, where the dialect will assume “READ COMMITTED” is the default isolation level as was the case prior to SQLAlchemy 1.3.21. However, explicit use of the Connection.get_isolation_level() method must now necessarily raise an exception, as Oracle databases with this restriction explicitly disallow the user from reading the current isolation level.
Redis 6.0.10
============
Upgrade urgency MODERATE: several bugs with moderate impact are fixed,
Here is a comprehensive list of changes in this release compared to 6.0.9.
Command behavior changes:
* SWAPDB invalidates WATCHed keys
* SORT command behaves differently when used on a writable replica
* EXISTS should not alter LRU
In Redis 5.0 and 6.0 it would have touched the LRU/LFU of the key.
* OBJECT should not reveal logically expired keys
Will now behave the same TYPE or any other non-DEBUG command.
* GEORADIUS[BYMEMBER] can fail with -OOM if Redis is over the memory limit
Other behavior changes:
* Sentinel: Fix missing updates to the config file after SENTINEL SET command
* CONFIG REWRITE is atomic and safer, but requires write access to the config file's folder
This change was already present in 6.0.9, but was missing from the release notes.
Bug fixes with compatibility implications (bugs introduced in Redis 6.0):
* Fix RDB CRC64 checksum on big-endian systems
If you're using big-endian please consider the compatibility implications with
RESTORE, replication and persistence.
* Fix wrong order of key/value in Lua's map response
If your scripts use redis.setresp() or return a map (new in Redis 6.0), please
consider the implications.
Bug fixes:
* Fix an issue where a forked process deletes the parent's pidfile
* Fix crashes when enabling io-threads-do-reads
* Fix a crash in redis-cli after executing cluster backup
* Handle output buffer limits for module blocked clients
Could result in a module sending reply to a blocked client to go beyond the limit.
* Fix setproctitle related crashes.
Caused various crashes on startup, mainly on Apple M1 chips or under instrumentation.
* Backup/restore cluster mode keys to slots map for repl-diskless-load=swapdb
In cluster mode with repl-diskless-load, when loading failed, slot map wouldn't
have been restored.
* Fix oom-score-adj-values range, and bug when used in config file
Enabling setting this in the config file in a line after enabling it, would
have been buggy.
* Reset average ttl when empty databases
Just causing misleading metric in INFO
* Disable rehash when Redis has child process
This could have caused excessive CoW during BGSAVE, replication or AOFRW.
* Further improved ACL algorithm for picking categories
Output of ACL GETUSER is now more similar to the one provided by ACL SETUSER.
* Fix bug with module GIL being released prematurely
Could in theory (and rarely) cause multi-threaded modules to corrupt memory.
* Reduce effect of client tracking causing feedback loop in key eviction
* Fix cluster access to unaligned memory (SIGBUS on old ARM)
* Fix saving of strings larger than 2GB into RDB files
Additional improvements:
* Avoid wasteful transient memory allocation in certain cases
Platform / toolchain support related improvements:
* Fix crash log registers output on ARM.
* Add a check for an ARM64 Linux kernel bug
Due to the potential severity of this issue, Redis will print log warning on startup.
* Raspberry build fix.
New configuration options:
* oom-score-adj-values config can now take absolute values (besides relative ones)
Module related fixes:
* Moved RMAPI_FUNC_SUPPORTED so that it's usable
* Improve timer accuracy
* Allow '\0' inside of result of RM_CreateStringPrintf
5.3.14
Security Notes:
Functionality added or changed:
* Unit tests will allocate/deallocate STMT/DBC/ENV for each test
* Added processing of new UTF8MB4 collations
Bugs fixed:
* myodbc-installer does not show all DSN options (Bug #29753227/95290)
* MASTER: Crash noticed in SQLSetPos (Bug #29630465)
Built using MySQL 5.7.28
5.3.13
Security Notes:
* Connector/ODBC 5.3.13 Commercial upgrades the linked OpenSSL
library to version 1.0.2r which has been publicly reported
as not vulnerable to CVE-2019-1559
(Bug #29489006, CVE-2019-1559)
Functionality added or changed:
Bugs fixed:
* SQL_NO_DATA when fetching VARCHAR(500) with filter
(Bug# 29512548/94545)
Built using MySQL 5.7.26
5.3.12
Security Notes:
Functionality added or changed:
* New connection option for ODBC driver to enable LOAD DATA LOCAL INFILE
Bugs fixed:
* Dynamic linking is broken in MyODBC 5.3.11 (Bug# 28609434/92319)
* Crash in SQLBulkOperations when NO_SSPS is set to 0 (Bug #28289320)
Built using MySQL 5.7.25
5.3.11
Security Notes:
* Fix issues found by Fortify (WL #11829)
Functionality added or changed:
* Fixes in ODBC 5.3 from 8.0 code merge (WL #12199)
* Make sure ODBC 5.3 works with new 8.0 auth. mechanism. (WL #11962)
Bugs fixed:
* Source character set not supported by client error on SHOW TABLES command
(Bug# 28116892/90984)
* SQLColAttribute/SQL_DESC_TYPE_NAME text instead of longtext for
longtext col (Bug# 11761407/53900)
* Connector uses UTF8 charset instead of UTF8MB4 (Bug# 28204756)
* SQLMoreResults does not set statement errors correctly
(Bug# 11757423/49466)
* Master: Connection fails for cache256 user when GET_SERVER_PUBLIC_KEY=1
(Bug# 28359632)
Built using MySQL 5.7.23
5.3.10
Security Notes:
Functionality added or changed:
* Build ODBC Connector with libmysqlclient linked dynamically (WL #11105)
Bugs fixed:
* ODBC Driver issue with SELECT for UPDATE (Bug# 26646688/87457)
* Contribution: Compilation fixes for MySQL 5.5 (Bug# 26633971/87413)
* Contribution: Fix truncated "SSL Certificate Authority" label
(Bug# 26579169/87325)
* OpenRecordset leaking memory client side on Windows ODBC Client
(Bug# 27155880/86473)
* MySQL Connector/ODBC 5.2.5 - Command Timeout does not work
(Bug# 26474362/69416)
* Calling MySQLDrivercConnect with a NULL pcbConnStrOut causes a crash
(Bug# 27101767/88371)
Built using MySQL 5.7.20
5.3.9
Security Notes:
Functionality added or changed:
* Added two new CMake build options. STATIC_MSVCRT to switch /MT and /MD
compiler options in Windows. WITH_NODEFAULTLIB to specify the
/NODEFAULTLIB linker option. (WL# 10890)
Bugs fixed:
* Segmentation fault in SQLFetch() when used with dynamic cursor
(Bug# 18805392)
* SQLExecute() after SQLFreeStmt(SQL_RESET_PARAMS) results
in assert failure (Bug# 19148246)
* SQLForeignKeys() crashing when SQL_MODE='ANSI_QUOTES'
(Bug# 18641824)
* SQLForeignKeys() returns empty result with NO_I_S=0
(Bug# 26388694)
Built using MySQL 5.7.19
----
5.3.8
Security Notes:
* Connector/ODBC 5.3.8 Commercial upgrades the linked OpenSSL
library to version 1.0.2k which has been publicly reported
as not vulnerable to CVE-2017-3732
(http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3732)
(Bug #25615448, CVE-2017-3732)
Functionality added or changed:
* Added a new connection option NO_DATE_OVERFLOW to control returning
of errors when the TIMESTAMP structure used for DATE column contains
non-zero time part (Bug# 25386024)
Bugs fixed:
* SQL_ATTR_MAX_ROWS applies to all result sets on the statement,
and not connection (Bug# 17259397/69554)
* SQLTABLES patch (Bug 13914518) has to be extended for NO_I_S case
(Bug# 14005343)
* Connector/ODBC does not send correct error message when 2006 error occurs
(Bug #25671389)
* Error in Windows Setup Wizard Custom Setup Dialog
(Bug# 25247807/84190)
* Contents in embedded help for myodbc-installer are outdated
(Bug# 18896110/72852)
* SQLGetData() with invalid column number crashes (Bug# 18636600)
* Assert failure in SQLSetDescField() API (Bug# 18641633)
* Metadata functions crash when the catalog/table/column name is long
(Bug #18796005)
* Prefetch causes syntax errors in select queries with parameters
(Bug# 17386788)
Built using MySQL 5.7.18
----
5.3.7
Security Notes:
* Connector/ODBC 5.3.7 Commercial upgrades the linked OpenSSL
library to version 1.0.2j which has been publicly reported
as not vulnerable to CVE-2016-6304
(http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6304)
(Bug #24753385, CVE-2016-6304)
Functionality added or changed:
* Added new options to control TLS versions for connecting:
NO_TLS_1_0, NO_TLS_1_1, NO_TLS_1_2. By Default all TLS versions are enabled
and options allow to disable using of a particular TLS version.
(Bug# 23496903/81640)
* Added a new option SSLMODE to set the SSL mode before connection is made.
The option value can be set to any of the follwing: DISABLED, PREFERRED,
REQUIRED, VERIFY_CA, VERIFY_IDENTITY. This option will override
the deprecated SSLVERIFY and SSL_ENFORCE.
(Bug# 23497043/81641)
Bugs fixed:
* Assertion in ODBC Driver when calling mysql_stmt_close() on a broken
connection (Bug# 25109356/83858)
* Connector ODBC does not build with newer CMake (Bug# 22746557)
* Installation fails in OSX El Capitan (23123503/81113)
Built using MySQL 5.7.17.
----
5.3.6
Functionality added or changed:
* Keywords specific to MySQL server 5.7 (WL#7992)
* Implement SQL_ATTR_QUERY_TIMEOUT statement attribute (WL#7991)
* Added DEFAULT_AUTH and PLUGIN_DIR options in connection parameters.
* Added DISABLE_SSL_DEFAULT connection parameter to disable
connecting through SSL by default.
* Added SSL_ENFORCE connection parameter to enforce SSL connection.
Bugs fixed:
* ODBC Driver not parsing comments correctly (Bug# 16613308/53891)
* Calling SQLGetDiagField with DIAGIDENTIFIER SQL_DIAG_ROW_COUNT always
returns 0 (Bug #11750296/40771)
* ADO hangs when using MySQL ODBC 5.3 ANSI Driver with French characters
(Bug# 20526062)
* Connector/ODBC fails to build when using libmysqlclient 5.7
(Bug# 20685833/76261)
* malloc/free mismatch in MySqlGetPrivateProvileStringW
(Bug# 21074676/76984)
----
5.3.5
Security Notes:
* Connector/ODBC 5.3.5 Commercial upgrades the linked OpenSSL
library to version 1.0.1m which has been publicly reported
as not vulnerable to CVE-2015-0286
(http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0286).
Since the only change in Connector/ODBC 5.3.5 is the inclusion
of OpenSSL libraries publicly reported as unaffected by
CVE-2015-0286, and since Oracle-produced MySQL Community
builds use YaSSL libraries which have been reported as not
affected by CVE-2015-0286, Oracle will not produce builds for
Connector/ODBC Community for version 5.3.5. This means the
Community edition of Connector/ODBC will skip version 5.3.5.
(Bug #20747740, CVE-2015-0286)
----
5.3.4
Functionality added or changed:
* New ODBC connection option to specify the location of RSA public key
(WL #7911)
Bugs fixed:
* SSL CA Path cannot be selected in Linux GUI (Bug #18813389/72716)
----
5.3.3
Functionality added or changed:
Bugs fixed:
* Seg Fault in SQLForeignKeys() when column name contains special characters
(Bug #18286118)
* Add NULL handle checks in ODBC API functions (WL #7807)
----
=== 5.40.0 (2021-01-01)
* Support UPDATE FROM syntax in SQLite 3.33.0+ (jeremyevans)
* Have pg_interval extension work with ActiveSupport 6.1 (jeremyevans)
* Have date_arithmetic extension work with ActiveSupport 6.1 (jeremyevans)
* Avoid method redefinition warnings in verbose warning mode (jeremyevans)
=== 5.39.0 (2020-12-01)
* Support :clustered option for primary key and unique constraints on Microsoft SQL Server (jeremyevans)
* Do not modify the size of binary columns when using set_column_allow_null on Microsoft SQL Server (jeremyevans) (#1736)
* Add a fork safety guide with more detail on how to use Sequel with libraries that fork (janko) (#1733)
* Make the roots_dataset method in the tree plugin work with queries using joins (jeremyevans) (#1731)
* Make Database#tables return partitioned tables on PostgreSQL 10+ (epoberezhny) (#1729, #1730)
=== 5.38.0 (2020-11-01)
* Do not add new Database instances to Sequel::DATABASES if the test connection fails (jeremyevans) (#1727)
* Support the newer com.mysql.cj.jdbc.Driver in the jdbc/mysql adapter (jeremyevans)
* Do not swallow disconnect errors in Database#create_or_replace_view or Database#create_table* on Oracle (jeremyevans)
* Only rescue non-disconnect Sequel::DatabaseErrors in Postgres::Database#server_version (jeremyevans) (#1724)
* Make the single_table_inheritance and prepared_statements plugins work if loaded into the same class (jeremyevans) (#1721)
## 6.1.0: 2020-12-24 {#release-6-1-0}
### Improvements
* Changed to use `:use_paged_results` option value by default.
[GitHub#189][Reported by Kevin McCormack]
### Thanks
* Kevin McCormack
## 6.0.4: 2020-12-06 {#release-6-0-4}
### Improvements
* Enabled concurrency by default.
[GitHub#188][Reported by Kevin McCormack]
7.3.0
- `stream_to` now quotes and escapes its table name.
- Removed `transaction_base::classname()`. Did anyone ever use it?
- Internal reorg of the `transaction` and `transactionfocus` hierarchies.
- Removed the only case of virtual inheritance, related to `namedclass`.
- Internal `concat()` for faster, simpler string concatentation.
- Fix compile omission in string conversions for `nullptr_t`.
- `pqxx::size_buffer()` can now size multiple values at once.
- `multi_to_string()` to convert multiple values into one `std::string`.
- Implicit `zview` constructor from `char const *`. (#389)
- Many `std::string&` parameters are now `zview` or `std::string_view`.
- Now checking statement parameter lengths for overflow.
- `#include <array>` in connection.cxx. (#394)
7.2.1
- Fix infinite loop in converting `char *` to string. (#377)
- Deprecated `namedclass`.
- Convert an entire row using `row::as<type...>()`.
- Internal rework of `field::to()` and `field::as()` functions.
- Some more warning options in maintainer mode.
- Removed the old, DocBook-based tutorial.
- Fixed wrong `query` and SQLSTATE params to some exceptions. (#378)
Version 1.19 - 2020-12-23
* Pre-read the memory mapped regions on systems that support it.
This speeds up operations on big databases.
* gdbmtool: tagged initialization of structured data
Initializers for structured data can be given in tagged form, e.g.:
store somekey { status=2, id={a,u,x}, name="foo" }
* Bugfixes:
** Preserve locking type during database reorganization
3.34.0-r1
Windows MSI installer files are now provided in addition to the exe files (APSW issue 294), as well as wheels for Python 3.6+. Python 3.9 binaries are also now available. The wheels can be installed via pip.
Added Connection.txn_state()
Added constants:
SQLITE_IOERR_CORRUPTFS
0.16.19
- Replace set `TZ` environment variable to `TIMEZONE` to avoid affecting global timezone.
- Allow passing module objects to `models_paths` param of `Tortoise.init_models()`.
- Implement `PydanticMeta.backward_relations`.
- Allow overriding `PydanticMeta` in `PydanticModelCreator`.
- Fixed make_native typo to make_naive in timezone module
- 0.49 | 2020-11-13
- dependency clarified: state range
Previously, the README file intimated that any Guile 1.4.x and
later would work w/ Guile-PG. This has now been clarified to
state the actual working range (1.4.x to 2.0.x, inclusive).
We have plans for adding support for 2.2.x (and maybe 3.x) in
the near to middling future.
See also file test/OK.
- Guile "auto-compilation" suppressed
In all three phases: configuration, build, and test, Guile 2.x
"auto-compilation" of .scm to .go files is suppressed by setting
the env var ‘GUILE_AUTO_COMPILE=0’.
We will do intentional compilation at some point, as soon as we
figure out how to DTRT. See project CMOD-PLAY for experiments.
packaging changes: PostgresQL 9.5 is no longer supported.
Upstream NEWS:
PostGIS 3.1.0
2020/12/18
This version requires PostgreSQL 9.6 or higher and GEOS 3.6 or higher
Additional features are enabled if you are running GEOS 3.9.
* Breaking changes *
- #4737, Bump minimum protobuf-c requirement to 1.1.0 (Raúl Marín)
The configure step will now fail if the requirement isn't
met or explicitly disabled (--without-protobuf)
- #4258, Separated postgis_sfcgal from postgis
into its own lib file and extension (Regina Obe)
- #4577, Drop support for PostgreSQL 9.5 (Raúl Marín)
- #4601, ST_TileEnvelope signature changed.
- #3057, ST_Force3D, ST_Force3DZ, ST_Force3DM and ST_Force4D signatures changed.
* Deprecated signatures *
- Function postgis_svn_version() replaced by postgis_lib_revision()
(Sandro Santilli)
- #4214, Deprecated ST_Count(tablename,...), ST_ApproxCount(tablename, ...)
ST_SummaryStats(tablename, ..),
ST_Histogram(tablename, ...), ST_ApproxHistogram(tablename, ...),
ST_Quantile(tablename, ...), ST_ApproxQuantile(tablename, ...) removed.
(Darafei Praliaskouski)
* New features*
- #4687, (GEOS 3.9+) MaximumInscribedCircle (Paul Ramsey)
- (GEOS 3.9+) Optional gridSize parameter to ST_Union, ST_UnaryUnion,
ST_Difference, ST_Intersection, ST_SymDifference, ST_Subdivide
for overlay with exact tolerance (Sandro Santilli)
- #4624, ST_HexagonGrid and ST_SquareGrid, set returning functions to
generate tilings of the plane (Paul Ramsey)
- #4624, ST_Hexagon and ST_Square, shape generators (Paul Ramsey)
- #4804, (GEOS 3.9+) ST_ReducePrecision allows valid precision reduction
(Paul Ramsey)
- #4710, ST_ClusterKMeans now works with 3D geometries (Darafei Praliaskouski)
- #4801, ST_ClusterKMeans supports weights in POINT[Z]M geometries
(Darafei Praliaskouski)
- #4805, _ST_SortableHash exposed to work around parallel soring performance issue
in Postgres. If your table is huge, use ORDER BY _ST_SortableHash(geom)
instead of ORDER BY geom to make parallel sort faster (Darafei Praliaskouski)
- #4625, Correlation statistics now calculated.
Run ANALYZE for BRIN indexes to start kicking in.
(Darafei Praliaskouski)
- #4698, Add a precision parameter to ST_AsEWKT (Raúl Marín)
* Enhancements *
- #4789, Sped up TopoJSON output for areal TopoGeometry with
many holes (Sandro Santilli)
- #4758, Improved topology noding robustness (Sandro Santilli)
- Make ST_Subdivide interruptable (Sandro Santilli)
- #4660, Changes in double / coordinate printing (Raúl Marín)
- Use the shortest representation (enough to guarantee roundtrip).
- Uses scientific notation for absolute numbers smaller than 1e-8.
The previous behaviour was to output 0 for absolute values smaller than
1e-12 and fixed notation for anything bigger than that.
- Uses scientific notation for absolute numbers greater than 1e+15
(same behaviour).
- The precision parameter now also affects the scientific notation
(before it was fixed [5-8]).
- All output functions now respect the requested precision (without
any limits).
- The default precision is the same (9 for GeoJSON, 15 for everything else).
- #4746, Micro optimizations to the serialization process (Raúl Marín)
- #4623, Optimize varlena returning functions (Raúl Marín)
- #4615, Speed up geojson output (Raúl Marín)
- #4737, Improve performance and reduce memory usage in ST_AsMVT, especially in
queries involving parallelism (Raúl Marín)
- #4719, Fail fast when srids don't match ST_Intersection(geometry,raster)
Also schema qualify calls in function. (Regina Obe)
- #4784, Add ST_CollectionExtract(geometry) with default behaviour of
extracting the components of highest coordinate dimension. (Paul Ramsey)
- #4675, topology.GetRingEdges now implemented in C (Sandro Santilli)
- #4672, Cache getSRSbySRID and getSRIDbySRS for better performance (Raúl Marín)
- #4676, #4657 Avoid decompressing toasted geometries to read only the header
(Raúl Marín)
- #4677, Share gserialized objects between different cache types (Raúl Marín)
- #4601, Add ST_TileEnvelope margin argument (Yuri Astrakhan)
- #2972, Add quiet mode (-q) to pgsql2shp (Kristian Thy)
- #3057, Optional value params for Force3D*, Force4D functions (Kristian Thy)
- #4569, Allow unknown SRID geometry insertion into typmod SRID column (Paul Ramsey)
- #4149, ST_Simplify(geom, 0) is now O(N).
ST_Affine (ST_Translate, ST_TransScale, ST_Rotate) optimized.
ST_SnapToGrid optimized. (Darafei Praliaskouski)
- #4656, Cast a geojson_text::geometry for implicit GeoJSON ingestion (Raúl Marín)
1.3.21
orm
[orm] [bug]
Added a comprehensive check and an informative error message for the case where a mapped class, or a string mapped class name, is passed to relationship.secondary. This is an extremely common error which warrants a clear message.
Additionally, added a new rule to the class registry resolution such that with regards to the relationship.secondary parameter, if a mapped class and its table are of the identical string name, the Table will be favored when resolving this parameter. In all other cases, the class continues to be favored if a class and table share the identical name.
[orm] [bug]
Fixed bug in Query.update() where objects in the _ormsession.Session that were already expired would be unnecessarily SELECTed individually when they were refreshed by the “evaluate”synchronize strategy.
[orm] [bug]
Fixed bug involving the restore_load_context option of ORM events such as InstanceEvents.load() such that the flag would not be carried along to subclasses which were mapped after the event handler were first established.
sql
[sql] [bug]
A warning is emmitted if a returning() method such as Insert.returning() is called multiple times, as this does not yet support additive operation. Version 1.4 will support additive operation for this. Additionally, any combination of the Insert.returning() and ValuesBase.return_defaults() methods now raises an error as these methods are mutually exclusive; previously the operation would fail silently.
[sql] [bug]
Fixed structural compiler issue where some constructs such as MySQL / PostgreSQL “on conflict / on duplicate key” would rely upon the state of the Compiler object being fixed against their statement as the top level statement, which would fail in cases where those statements are branched from a different context, such as a DDL construct linked to a SQL statement.
postgresql
[postgresql] [usecase]
Added new parameter ExcludeConstraint.ops to the ExcludeConstraint object, to support operator class specification with this constraint. Pull request courtesy Alon Menczer.
[postgresql] [bug] [mysql]
Fixed regression introduced in 1.3.2 for the PostgreSQL dialect, also copied out to the MySQL dialect’s feature in 1.3.18, where usage of a non Table construct such as text() as the argument to Select.with_for_update.of would fail to be accommodated correctly within the PostgreSQL or MySQL compilers.
mysql
[mysql] [bug] [reflection]
Fixed issue where reflecting a server default on MariaDB only that contained a decimal point in the value would fail to be reflected correctly, leading towards a reflected table that lacked any server default.
[mysql] [sql]
Added missing keywords to the RESERVED_WORDS list for the MySQL dialect: action, level, mode, status, text, time. Pull request courtesy Oscar Batori.
sqlite
[sqlite] [usecase]
Added sqlite_with_rowid=False dialect keyword to enable creating tables as CREATE TABLE … WITHOUT ROWID. Patch courtesy Sean Anderson.
mssql
[mssql] [bug]
Fixed bug where a CREATE INDEX statement was rendered incorrectly when both mssql-include and mssql_where were specified. Pull request courtesy @Adiorz.
[mssql] [bug]
Added SQL Server code “01000” to the list of disconnect codes.
[mssql] [reflection] [sqlite]
Fixed issue with composite primary key columns not being reported in the correct order. Patch courtesy @fulpm.
oracle
[oracle] [usecase]
Implemented support for the SERIALIZABLE isolation level for Oracle databases, as well as a real implementation for Connection.get_isolation_level().
2.23.0:
[CHANGE] UI: Make the React UI default.
[CHANGE] Remote write: The following metrics were removed/renamed in remote write.
prometheus_remote_storage_succeeded_samples_total was removed and prometheus_remote_storage_samples_total was introduced for all the samples attempted to send.
prometheus_remote_storage_sent_bytes_total was removed and replaced with prometheus_remote_storage_samples_bytes_total and prometheus_remote_storage_metadata_bytes_total.
prometheus_remote_storage_failed_samples_total -> prometheus_remote_storage_samples_failed_total .
prometheus_remote_storage_retried_samples_total -> prometheus_remote_storage_samples_retried_total.
prometheus_remote_storage_dropped_samples_total -> prometheus_remote_storage_samples_dropped_total.
prometheus_remote_storage_pending_samples -> prometheus_remote_storage_samples_pending.
[CHANGE] Remote: Do not collect non-initialized timestamp metrics.
[FEATURE] [EXPERIMENTAL] Remote write: Allow metric metadata to be propagated via remote write. The following new metrics were introduced: prometheus_remote_storage_metadata_total, prometheus_remote_storage_metadata_failed_total, prometheus_remote_storage_metadata_retried_total, prometheus_remote_storage_metadata_bytes_total.
[ENHANCEMENT] Remote write: Added a metric prometheus_remote_storage_max_samples_per_send for remote write.
[ENHANCEMENT] TSDB: Make the snapshot directory name always the same length.
[ENHANCEMENT] TSDB: Create a checkpoint only once at the end of all head compactions.
[ENHANCEMENT] TSDB: Avoid Series API from hitting the chunks.
[ENHANCEMENT] TSDB: Cache label name and last value when adding series during compactions making compactions faster.
[ENHANCEMENT] PromQL: Improved performance of Hash method making queries a bit faster.
[ENHANCEMENT] promtool: tsdb list now prints block sizes.
[ENHANCEMENT] promtool: Calculate mint and maxt per test avoiding unnecessary calculations.
[ENHANCEMENT] SD: Add filtering of services to Docker Swarm SD.
[BUGFIX] React UI: Fix button display when there are no panels.
[BUGFIX] PromQL: Fix timestamp() method for vector selector inside parenthesis.
[BUGFIX] PromQL: Don't include rendered expression on PromQL parse errors.
[BUGFIX] web: Fix panic with double close() of channel on calling /-/quit/.
[BUGFIX] TSDB: Fixed WAL corruption on partial writes within a page causing invalid checksum error on WAL replay.
[BUGFIX] Update config metrics prometheus_config_last_reload_successful and prometheus_config_last_reload_success_timestamp_seconds right after initial validation before starting TSDB.
[BUGFIX] promtool: Correctly detect duplicate label names in exposition.
Changes in Version 3.11.2
Issues Resolved
Version 3.11.2 includes a number of bugfixes. Highlights include:
Fixed a memory leak caused by failing SDAM monitor checks on Python 3 (PYTHON-2433).
Fixed a regression that changed the string representation of BulkWriteError (PYTHON-2438).
Fixed a bug that made it impossible to use bson.codec_options.CodecOptions.with_options() and with_options() on some early versions of Python 3.4 and Python 3.5 due to a bug in the standard library implementation of collections.namedtuple._asdict() (PYTHON-2440).
Fixed a bug that resulted in a TypeError exception when a PyOpenSSL socket was configured with a timeout of None (PYTHON-2443).
Changes in Version 3.11.1
Version 3.11.1 adds support for Python 3.9 and includes a number of bugfixes. Highlights include:
Support for Python 3.9.
Initial support for Azure and GCP KMS providers for client side field level encryption is in beta. See the docstring for MongoClient, AutoEncryptionOpts, and encryption. Note: Backwards-breaking changes may be made before the final release.
Fixed a bug where the bson.json_util.JSONOptions API did not match the bson.codec_options.CodecOptions API due to the absence of a bson.json_util.JSONOptions.with_options() method. This method has now been added.
Fixed a bug which made it impossible to serialize BulkWriteError instances using pickle.
Fixed a bug wherein PyMongo did not always discard an implicit session after encountering a network error.
Fixed a bug where connections created in the background were not authenticated.
Fixed a memory leak in the bson module when using a TypeRegistry.
Changes in Version 3.11.0
Version 3.11 adds support for MongoDB 4.4 and includes a number of bug fixes. Highlights include:
Support for OCSP (Online Certificate Status Protocol).
Support for PyOpenSSL as an alternative TLS implementation. PyOpenSSL is required for OCSP support. It will also be installed when using the “tls” extra if the version of Python in use is older than 2.7.9.
Support for the MONGODB-AWS authentication mechanism.
Support for the directConnection URI option and kwarg to MongoClient.
Support for speculative authentication attempts in connection handshakes which reduces the number of network roundtrips needed to authenticate new connections on MongoDB 4.4+.
Support for creating collections in multi-document transactions with create_collection() on MongoDB 4.4+.
Added index hinting support to the replace_one(), update_one(), update_many(), find_one_and_replace(), find_one_and_update(), delete_one(), delete_many(), and find_one_and_delete() commands.
Added index hinting support to the ReplaceOne, UpdateOne, UpdateMany, DeleteOne, and DeleteMany bulk operations.
Added support for bson.binary.UuidRepresentation.UNSPECIFIED and MongoClient(uuidRepresentation='unspecified') which will become the default UUID representation starting in PyMongo 4.0. See Handling UUID Data for details.
Added the background parameter to pymongo.database.Database.validate_collection(). For a description of this parameter see the MongoDB documentation for the validate command.
Added the allow_disk_use parameters to pymongo.collection.Collection.find().
Added the hedge parameter to PrimaryPreferred, Secondary, SecondaryPreferred, Nearest to support disabling (or explicitly enabling) hedged reads in MongoDB 4.4+.
Fixed a bug in change streams that could cause PyMongo to miss some change documents when resuming a stream that was started without a resume token and whose first batch did not contain any change documents.
Fixed an bug where using gevent.Timeout to timeout an operation could lead to a deadlock.
Deprecations:
Deprecated the oplog_replay parameter to pymongo.collection.Collection.find(). Starting in MongoDB 4.4, the server optimizes queries against the oplog collection without requiring the user to set this flag.
Deprecated pymongo.collection.Collection.reindex(). Use command() to run the reIndex command instead.
Deprecated pymongo.mongo_client.MongoClient.fsync(). Use command() to run the fsync command instead.
Deprecated pymongo.mongo_client.MongoClient.unlock(). Use command() to run the fsyncUnlock command instead. See the documentation for more information.
Deprecated pymongo.mongo_client.MongoClient.is_locked. Use command() to run the currentOp command instead. See the documentation for more information.
Unavoidable breaking changes:
GridFSBucket and GridFS do not support multi-document transactions. Running a GridFS operation in a transaction now always raises the following error: InvalidOperation: GridFS does not support multi-document transactions
repmgr 5.2.1 is a minor release.
A.1.1. Improvements
repmgr standby clone: option --recovery-min-apply-delay added, overriding any setting present in repmgr.conf.
A.1.2. Bug fixes
Configuration: fix parsing of replication_type configuration parameter.
repmgr standby clone: handle case where postgresql.auto.conf is absent on the source node.
repmgr standby clone: in PostgreSQL 11 and later, an existing data directory's permissions will not be changed to 0700 if they are already set to 0750.
repmgrd: prevent termination when local node not available and standby_disconnect_on_failover is set.
repmgrd: ensure reconnect_interval is correctly handled.
repmgr witness --help: fix witness unregister description.
Slony 2.2.10 now available
The next bug fix release in the 2.2.x series is now available. This release includes the following
* Remove unsupported warning with PG13
5.1.0 (2020-12-03)
==================
Features
--------
- Support ``GenericAliases`` (``MultiDict[str]``) for Python 3.9+
Bugfixes
--------
- Synchronize the declared supported Python versions in ``setup.py`` with actually supported and tested ones.
Slony 2.2.9 now available
The next bug fix release in the 2.2.x series is now available. This release includes the following
* fix slonik_build_env.pl so it works with PG11+
* Remove unsupported warning with PG12
* Fix compiler warnings with -fno-common
wal2json is an output plugin for logical decoding. It means that the plugin
have access to tuples produced by INSERT and UPDATE. Also, UPDATE/DELETE old
row versions can be accessed depending on the configured replica identity.
Changes can be consumed using the streaming protocol (logical replication
slots) or by a special SQL API.
4.2.11:
Issues fixed in 4.2.11:
SERVER-43664: Speedup WiredTiger storage engine startup for many tables by optimizing WiredTigerUtil::setTableLogging()
SERVER-45938: Allow matching O/OU/DC in client x509 cert if clusterMode:keyFile
SERVER-48523: Unconditionally check the first entry in the oplog when attempting to resume a change stream
SERVER-51120: Find queries with SORT_MERGE incorrectly sort the results when the collation is specified
WT-6507: Exit cache eviction worker after our operation has timed out
All JIRA issues closed in 4.2.11
4.2.10:
Issues fixed in 4.2.10:
SERVER-26726: Check number of arguments for createIndex() and throw error if more than two arguments
SERVER-31368: Log time spent waiting for other shards in merge cursors aggregation stage
SERVER-37422: Log balancer start and stop events in the actionlog
SERVER-40317: $facet execution has no limit on how much memory it can consume
SERVER-43233: Add ability to request only specific attribute(s) for the LDAP groups
SERVER-47469: applyOps does not take exclusive lock for views operation
SERVER-50463: Make PooledLDAPConnection::refresh take self-ownership
SERVER-51041: Throttle starting transactions for secondary reads
All JIRA issues closed in 4.2.10
4.2.9:
Issues fixed in 4.2.9:
SERVER-44051: getShardDistribution() does not report “Collection XYZ is not sharded” on dropped but previously sharded collections
SERVER-45610: Some reads work while system is RECOVERING
SERVER-47714: Secondary asserts on system.profile collection with WiredTigerRecordStore::insertRecord 95: Operation not supported
SERVER-48067: Reduce memory consumption for unique index builds with large numbers of non-unique keys
SERVER-49233: Introduce a flag to toggle the logic for bumping collection’s major version during split
WT-6480: Fix a bug where files without block modification information were repeatedly copied at each incremental backup
All JIRA issues closed in 4.2.9
4.2.8:
Issues fixed in 4.2.8:
SERVER-46897: REMOVED node may never send heartbeat to fetch newest config
SERVER-47799: AsyncRequestsSender should update replica set monitor in between retries for InterruptedAtShutdown
SERVER-47994: Fix for numerical overflow in GeoHash
SERVER-48307: 3 Transactions that write to exactly one shard and read from one or more other shards may incorrectly indicate failure on retry after successful commit
WT-6366: Off-by-one overflow in block-modification bitmaps for incremental backup
All JIRA issues closed in 4.2.8
mongo-c-driver 1.17.3
=====================
Bug fixes:
* Do not send session ID on GSSAPI auth commands.
* Fix build against zlib when zlib is installed in non-standard location.
* Fix build when source directory path contains a space.
* Fix a platform-specific bug causing mongoc_client_pool_pop to block indefinitely if all clients are checked out.
* Fix a possible buffer overflow with hostnames resolving to IPv6 addresses on OpenSSL.
mongo-c-driver 1.17.2
=====================
Bug fixes:
* Stop the SRV polling thread when an SRV URI is used to connect to a deployment other than a sharded cluster.
mongo-c-driver 1.17.1
=====================
Bug fixes:
* Fix SRV/TXT record lookup for DNS records exceeding 1024 bytes.
mongo-c-driver 1.17.0
=====================
This release adds support for MongoDB 4.4 servers.
Features:
* Support streamable server monitoring to reduce recovery time when the server topology changes.
* Support the MONGODB-AWS authentication mechanism.
* Support Online Certificate Status Protocol (OCSP).
* Support configuring hedged reads in read preferences.
* Reduce the number of round trips necessary for SCRAM and X509 authentication.
* Monitor servers in parallel when using a mongoc_client_pool_t instead of doing serial scans.
* Support the "hint" option in operations using the update, replace, delete, and findAndModify commands.
* Improve behavior for retryable writes.
* Improve resuming behavior of change streams on server errors.
* Remove restriction of 255 character collection namespaces.
Bug fixes:
* Fix criteria for resumable errors in change streams.
* Fix rare crashes when server is invalidated during authentication.
* Reject client session for mongoc_collection_estimated_document_count.
* Fix behavior of a SecondaryPreferred read preference for exhaust cursor operations against a sharded cluster. Prior to the fix, a nonzero maxStalenessSeconds would not trigger sending the read preference.
* Fix SRV polling. Prior to the fix, SRV polling did not properly apply newly discovered results.
* Fix checks for existing GridFS indexes to handle indexes created by the MongoDB shell.
* Fix possible use of invalidated streams during an unordered OP_QUERY bulk write, and when ending many pooled sessions at client destruction.
* Fix a crash when setting the crl_file TLS option for Secure Channel.
* Avoid emitting duplicate ServerChanged events when no change is observed during monitoring.
* Properly handle large SASL messages instead of erroring.
Notes:
* Deprecated "lib" prefixed artifacts are no longer produced when building on Windows.
SQLite Release 3.34.0
Added the sqlite3_txn_state() interface for reporting on the current transaction state of the database connection.
Enhance recursive common table expressions to support two or more recursive terms as is done by SQL Server, since this helps make queries against graphs easier to write and faster to execute.
Improved error messages on CHECK constraint failures.
CLI enhancements:
The .read dot-command now accepts a pipeline in addition to a filename.
Added options --data-only and --nosys to the .dump dot-command.
Added the --nosys option to the .schema dot-command.
Table name quoting works correctly for the .import dot-command.
The generate_series(START,END,STEP) table-valued function extension is now built into the CLI.
The .databases dot-command now show the status of each database file as determined by sqlite3_db_readonly() and sqlite3_txn_state().
Added the --tabs command-line option that sets .mode tabs.
The --init option reports an error if the file named as its argument cannot be opened. The --init option also now honors the --bail option.
Query planner improvements:
Improved estimates for the cost of running a DISTINCT operator.
When doing an UPDATE or DELETE using a multi-column index where only a few of the earlier columns of the index are useful for the index lookup, postpone doing the main table seek until after all WHERE clause constraints have been evaluated, in case those constraints can be covered by unused later terms of the index, thus avoiding unnecessary main table seeks.
The new OP_SeekScan opcode is used to improve performance of multi-column index look-ups when later columns are constrained by an IN operator.
The BEGIN IMMEDIATE and BEGIN EXCLUSIVE commands now work even if one or more attached database files are read-only.
Enhanced FTS5 to support trigram indexes.
Improved performance of WAL mode locking primitives in cases where there are hundreds of connections all accessing the same database file at once.
Enhanced the carray() table-valued function to include a single-argument form that is bound using the auxiliary sqlite3_carray_bind() interface.
The substr() SQL function can now also be called "substring()" for compatibility with SQL Server.
The syntax diagrams are now implemented as Pikchr scripts and rendered as SVG for improved legibility and ease of maintenance.
6.2.8:
* In Python 3.9, "find_unused_port" has been moved to
"test.support.socket_helper". Reported by Michał Górny.
* If we use "set_get_returns_none()" in the environment,
the value could not be correctly inherited by the child
databases. Reported by Patrick Laimbock and modern GCC
warnings.
* If you install this library under Python 3 >= 3.6, let
you know this is a legacy library and points you to
"berkeleydb" library.
Packaging changes: make bl3 refer to PGSQL_VERSION, not 12, reverting
an earlier change labeled "revbump" which does not make sense for such
a change.
Upstream changes: bugfixes
0.16.18
Support custom function in update.
Add Model.refresh_from_db.
Add timezone support, be careful to upgrade to this version, see docs for details.
Remove aerich in case of cyclic dependency.
PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24
Security Issues
* CVE-2020-25695: Multiple features escape "security restricted operation" sandbox
* CVE-2020-25694: Reconnection can downgrade connection security settings
* CVE-2020-25696: psql's \gset allows overwriting specially treated variables
Bug Fixes and Improvements
This update also fixes over 65 bugs that were reported in the last several months. Some of these issues only affect version 13, but may also apply to other supported versions.
Some of these fixes include:
Fix a breakage in the replication protocol by ensuring that two "command completion" events are expected for START_REPLICATION.
Ensure fsync is called on the SLRU caches that PostgreSQL maintains. This prevents potential data loss due to an operating system crash.
Fix ALTER ROLE usage for users with the BYPASSRLS permission.
ALTER TABLE ONLY ... DROP EXPRESSION is disallowed on partitioned tables when there are child tables.
Ensure that ALTER TABLE ONLY ... ENABLE/DISABLE TRIGGER does not apply to child tables.
Fix for ALTER TABLE ... SET NOT NULL on partitioned tables to avoid a potential deadlock in parallel pg_restore.
Fix handling of expressions in CREATE TABLE LIKE with inheritance.
DROP INDEX CONCURRENTLY is disallowed on partitioned tables.
Allow LOCK TABLE to succeed on a self-referential view instead of throwing an error.
Several fixes around statistics collection and progress reporting for REINDEX CONCURRENTLY.
Ensure that GENERATED columns are updated when any columns they depend on are updated via a rule or an updatable view.
Support hash partitioning with text array columns as partition keys.
Allow the jsonpath .datetime() method to accept ISO 8601-format timestamps.
During a "smart" shutdown, ensure background processes are not terminated until all foreground client sessions are completed, fixing an issue that broke the processing of parallel queries.
Several fixes for the query planner and optimizer.
Ensure that data is de-toasted before being inserted into a BRIN index. This could manifest itself with errors like "missing chunk number 0 for toast value NNN". If you have seen a similar error in an existing BRIN index, you should be able to correct it by using REINDEX on the index.
Fix the output of EXPLAIN to have the correct XML tag nesting for incremental sort plans.
Several fixes for memory leaks, including ones involving RLS policies, using CALL with PL/pgSQL, SIGHUP processing a configuration parameter that cannot be applied without a restart, and an edge-case for index lookup for a partition.
libpq can now support arbitrary-length lines in the .pgpass file.
On Windows, psql now reads the output of a backtick command in text mode, not binary mode, so it can now properly handle newlines.
Fix how pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb use complex connection-string parameters.
When the \connect command of psql reuses connection parameters, ensure that all non-overridden parameters from a previous connection string are also re-used.
Ensure that pg_dump collects per-column information about extension configuration tables, avoiding crashes when specifying --inserts.
Ensure that parallel pg_restore processes foreign keys referencing partitioned tables in the correct order.
Several fixes for contrib/pgcrypto, including a memory leak fix.
DB Browser for SQLite 3.12.1
This is the first bug fix release for our 3.12.x series.
There aren't any "super critical must upgrade" bugs fixed, so updating isn't urgent. 😄
The changes in this over the 3.12.0 release include:
Enhancements
Completely reworked interface for accessing DBHub.io
Add .Net DateTime.Ticks to list of supported display formats
Add more options for setting font sizes
New predefined settings for simplified window layout
Bug fixes
Fix loading of project files with empty filter values
Fix initial table view when using the -t / --table command line option
Add status message when opening a file from the recent file list (4dfe4f7)
Make sure to not show "NULL" for empty but non-NULL values in the Edit dialog
Fix plot being drawn before all data is loaded
Restore original default for having condition format in filter line (f28ecc0)
Fix default font in the format toolbar (c4b2ffc)
Improve binary detection for cases starting by chance by a BOM
Make sure the order of the statements in the SQL log is correct (05db901)
Fix executing selected SQL text when there are multi-byte characters
Fix executing SQL queries with compound operators
Fix SQL import of files with BOM
Also update schema when clicking the Refresh button in Browse Data tab (16c3d8d)
Select column in table results when column header is pressed
Tweak the output wording for command line options
Remove the default property of the cancel button in the "Fetching data..." dialog
Fix not being saved and not applied when modifying database cells in Windows external program (f2d8f79)
Fix incorrect display of SQL calltips containing non-US-ASCII characters (9f7851b)
Fix to 'Window Layout' options work properly
Building and packaging
Fix CMake warning during compilation (115aa00)
snap: Add environment variables to set Qt theme (7b5d652)
Updated to OpenSSL 1.1.1h for the Windows and macOS builds
Platform specific
No longer force Light theme on macOS when "Follow the desktop style" is chosen (508118f)
Keep registry key consistent on Windows
Allow use of integrated graphics card instead of high performance graphics card in macOS
Use native path separators in Preferences dialog (f38b829)
Added message box for informative command line arguments for Windows
2.22.1
* [BUGFIX] Fix potential "mmap: invalid argument" errors in loading the head chunks, after an unclean shutdown, by performing read repairs.
* [BUGFIX] Fix serving metrics and API when reloading scrape config.
* [BUGFIX] Fix head chunk size calculation for size based retention.
pkgsrc: changes: re-enable .la
There are some test issues, but it seems better to move to 0.48 than
stay at 0.47. If you are a pkgsrc user of guile-pg and disagree,
please speak up (and help test/fix!).
- 0.48 | 2020-10-26
- installation by default deletes the .la files
See README re "SOFIXFLAGS".
- configuration changes
- configure script tries to use pkg-config(1)
The configure script now tries to use pkg-config(1) to determine
directory values for the ‘-I’ and ‘-L’ compiler switches. The
standard way is still supported (see README).
- configure-time ‘INITDB’ specification
For "make check", you can specify to the configure script the
initdb(1) program to use with option ‘INITDB=/path/to/initdb’.
For example:
./configure INITDB=/usr/lib/postgresql/9.4/bin/initdb
This saves the value of ‘INITDB’ so you don't need to specify it
manually for each "make check" invocation (see README).
- builtin array variant types now have prefix-asterisk names
Previously, the builtin array variant types had names that end
in "[]" (i.e., one or more pairs of square braces). These now
have prefix-asterisk names.
(was) (now)
text[] *text
text[][] **text
int4[] *int4
aclitem[] *aclitem
Furthermore, old-style names are no longer supported. This is
concomitant w/ dropping of ‘define-db-col-type-array-variant’
(see below).
- dropped items
All these were announced in Guile-PG 0.47 (2015-02-23).
- module ‘(database postgres-resdisp)’
- proc ‘(database postgres) pg-lo-read’
- procs in module ‘(database postgres-types)’
- ‘dbcoltypes’
- ‘dbcoltype-lookup’
- ‘dbcoltype:stringifier’
- ‘dbcoltype:default’
- ‘dbcoltype:objectifier’
- ‘define-db-col-type-array-variant’
OpenLDAP 2.4.56
Fixed slapd to remove assert in certificateListValidate
Fixed slapd to remove assert in csnNormalize23
Fixed slapd to better parse ldapi listener URIs
3.14.0
This release has been a bit overdue and there are numerous small improvements
and bug-fixes. The bugfix that prompted this release is 2293, which is a
regression in the Django-inspired .filter() APIs that could cause some
filter expressions to be discarded from the generated SQL. Many thanks for the
excellent bug report, Jakub.
Add an experimental helper, shortcuts.resolve_multimodel_query(), for resolving multiple models used in a compound select query.
Add a lateral() method to select query for use with lateral joins.
Added support for nested transactions (savepoints) in cockroach-db (requires 20.1 or newer).
Automatically escape wildcards passed to string-matching methods.
Allow index-type to be specified on MySQL.
Added a new API, converter() to be used for specifying a function to use to convert a row-value pulled off the cursor.
Add set() and clear() method to the bitfield flag descriptor.
Add support for range types with IN and other expressions.
Support CTEs bound to compound select queries.
Bug-fixes
Fix to return related object id when accessing via the object-id descriptor, when the related object is not populated.
Fix to ensure we do not insert a NULL value for a primary key.
Fix to conditionally set the field/column on an added column in a migration.
Apply field conversion logic to model-class values.
Clone node before modifying it to be flat in an enclosed nodelist expr.
Fix an invalid item assignment in nodelist.
Fix an incorrect truthiness check used with save() and only=.
Fix regression in filter() where using both *args and **kwargs caused the expressions passed as args to be discarded.
These binaries are not installed in the official binary distributions.
We probably installed them as a side effect of using pax(1) to copy the
whole bin/ directory. Use ${INSTALL_PROGRAM} instead.
This PostgreSQL extension contains support functions to improve the performance
of Promscale. While Promscale will run without it, adding this extension will
cause it to perform better.
Promscale allows Prometheus to store data in a PostgreSQL instance using the
TimescaleDB extension. Promscale can also act directly as a
Prometheus Data Source for Grafana, or other software.
By allowing a user to use SQL, in addition to PromQL, this platform empowers
the user to ask complex analytical queries from their metrics data, and thus
extract more meaningful insights.
v0.16.0
-------
Feature release
* Improved performance for async iteration on cursors
* Support for deterministic user functions in Python 3.8+
* Reduced logging severity for exceptions returned from children
* Fix InvalidStateError when setting future results
* Allow user to catch exceptions from `close()`
* Tested under Python 3.9
repmgr 5.2.0 is a major release.
This release provides support for PostgreSQL 13, released in September 2020.
This release removes support for PostgreSQL 9.3, which was designated EOL in November 2018.
A.1.1. General improvements
Configuration: support include, include_dir and include_if_exists directives (see configuration file include directives).
repmgr standby switchover: Improve sanity check failure log output from the demotion candidate.
If database connection configuration is not consistent across all nodes, it's possible remote repmgr invocations (e.g. during switchover, from the promotion candidate to the demotion candidate) will not be able to connect to the database. This will now be explicitly reported as a database connection failure, rather than as a failure of the respective sanity check.
repmgr cluster crosscheck / repmgr cluster matrix: improve text mode output format, in particular so that node identifiers of arbitrary length are displayed correctly.
repmgr primary unregister: the --force can be provided to unregister an active primary node, provided it has no registered standby nodes.
repmgr standby clone: new option --verify-backup to run PostgreSQL's pg_verifybackup utility after cloning a standby to verify the integrity of the copied data (PostgreSQL 13 and later).
repmgr standby clone: when cloning from Barman, setting --waldir (PostgreSQL 9.6 and earlier: --xlogdir) in pg_basebackup_options will cause repmgr to create a WAL directory outside of the main data directory and symlink it from there, in the same way as would happen when cloning using pg_basebackup.
repmgr standby follow: In PostgreSQL 13 and later, a standby no longer requires a restart to follow a new upstream node.
The old behaviour (always restarting the standby to follow a new node) can be restored by setting the configuration file parameter standby_follow_restart to true.
repmgr node rejoin: enable a node to attach to a target node even the target node has a lower timeline (PostgreSQL 9.6 and later).
repmgr node rejoin: in PostgreSQL 13 and later, support pg_rewind's ability to automatically run crash recovery on a PostgreSQL instance which was not shut down cleanly.
repmgr node check: option --db-connection added to check if repmgr can connect to the database on the local node.
repmgr node check: report database connection error if the --optformat was provided.
Improve handling of pg_control read errors.
It is now possible to dump the contents of repmgr metadata tables with pg_dump.
A.1.2. repmgrd enhancements
Following additional parameters can be provided to failover_validation_command:
%n: node ID
%a: node name
%v: number of visible nodes
%u: number of shared upstream nodes
%t: total number of nodes
Configuration option always_promote (default: false) to control whether a node should be promoted if the repmgr metadata is not up-to-date on that node.
A.1.3. Bug fixes
repmgr standby clone: fix issue with cloning from Barman where the tablespace mapping file was not flushed to disk before attempting to retrieve files from Barman.
repmgr node rejoin: ensure that when verifying a standby node has attached to its upstream, the node has started streaming before confirming the success of the rejoin operation.
repmgrd: ensure primary connection is reset if same as upstream.
What's new in psycopg 2.8.6
- Fixed memory leak changing connection encoding to the current one.
- Fixed search of mxDateTime headers in virtualenvs.
- Added missing values from errorcodes.
- `cursor.query` reports the query of the last :sql:`COPY` opearation too.
- `~psycopg2.errorcodes` map and `~psycopg2.errors` classes updated to
PostgreSQL 13.
- Added wheel packages for ARM architecture.
- Wheel package compiled against OpenSSL 1.1.1g.
What's new in psycopg 2.8.5
- Fixed use of `!connection_factory` and `!cursor_factory` together.
- Added support for `~logging.LoggerAdapter` in
`~psycopg2.extras.LoggingConnection`.
- `~psycopg2.extensions.Column` objects in `cursor.description` can be sliced.
- Added AIX support.
- Fixed `~copy.copy()` of `~psycopg2.extras.DictCursor` rows
Redis 6.0.9
===========
Upgrade urgency: SECURITY if you use an affected platform (see below).
Otherwise the upgrade urgency is MODERATE.
This release fixes a potential heap overflow when using a heap allocator other
than jemalloc or glibc's malloc. See:
https://github.com/redis/redis/pull/7963
Other fixes in this release:
New:
* Memory reporting of clients argv
* Add redis-cli control on raw format line delimiter
* Add redis-cli support for rediss:// -u prefix
* Get rss size support for NetBSD and DragonFlyBSD
Behavior changes:
* WATCH no longer ignores keys which have expired for MULTI/EXEC
* Correct OBJECT ENCODING response for stream type
* Allow blocked XREAD on a cluster replica
* TLS: Do not require CA config if not used
Bug fixes:
* INFO report real peak memory (before eviction)
* Allow requirepass config to clear the password
* Fix config rewrite file handling to make it really atomic
* Fix excessive categories being displayed from ACLs
* Add fsync in replica when full RDB payload was received
* Don't write replies to socket when output buffer limit reached
* Fix redis-check-rdb support for modules aux data
* Other smaller bug fixes
Modules API:
* Add APIs for version and compatibility checks
* Add RM_GetClientCertificate
* Add RM_GetDetachedThreadSafeContext
* Add RM_GetCommandKeys
* Add Swapdb Module Event
* RM_GetContextFlags provides indication of being in a fork child
* RM_GetContextFlags document missing flags: MULTI_DIRTY, IS_CHILD
* Expose real client on connection events
* Minor improvements to module blocked on keys
0.16.17
Add on_delete in ManyToManyField.
Support F expression in annotate.
Fix QuerySet.select_related in case of join same table twice.
Integrate Aerich into the install.
Note that the 5.6 series will be end of life in February 2021. The
current major version is 8.0, which isn't in pkgsrc yet. You CAN NOT
upgrade directly from 5.6 to 8.0, therefore it is recommended for anybody
running 5.6 to upgrade to this version, then upgrade to 5.7.
Changes in MySQL 5.6.50 (2020-10-19, General Availability)
Functionality Added or Changed
LOCK TABLES privilege checking for views was improved. (Bug #31304432)
Bugs Fixed
InnoDB: In session started with START TRANSACTION WITH CONSISTENT
SNAPSHOT, a range query returned a truncated result. The end
range flag was not reset at the beginning of the index read
resulting in an aborted read and missing rows. (Bug #30950714,
Bug #98642)
References: This issue is a regression of: Bug #23481444.
In bootstrapping mode, certain multiple-statement transactions
could cause unexpected server behavior. (Bug #31650096)
Assigning CONCAT('') or CONCAT_WS('') to a variable set the
variable to NULL, not the empty string. (Bug #31320716, Bug
#99485, Bug #31413167, Bug #99722)
ORDER BY queries were not executed correctly when sort_buffer_size
and max_sort_length were set to values which caused the internal
limit on the maximum number of keys allowed per sort buffer to
be set to 0. (Bug #30175483)
The internal method Field_tiny::pack() did not always perform
bounds checking as expected. (Bug #29948029)
References: See also: Bug #31591391.
A large number of nested arguments in full-text search query
caused an error. (Bug #29929684)
An assertion could be raised when the SQL layer passed incorrect
information to InnoDB about the type of operation to be performed
on a temporary table. (Bug #22503696)
Upstream changes:
5.0.0 (2020-10-12)
Features
Provide wheels for aarch64, i686, ppc64le, s390x architectures on Linux as well as x86_64. #500
Provide wheels for Python 3.9. #534
Removal
Drop Python 3.5 support; Python 3.6 is the minimal supported Python version.
7.2.0
- You can now implicitly convert a `const std::string &` to `zview`.
- Replaced some overloads for C strings and C++ strings with `zview`.
- Deprecating `binarystring`. Use `std::basic_string<std::byte>` instead!
- Array parser did not recognise escaping in unquoted values.
- gcc10 test build fix: a result iterator is not the same thing as a `row`.
- Doc fix: field size does _not_ include terminating zero. (#356)
- Fix error message in `demangle_type_name`: printed result, not raw name.
- Fix compile warning in `demangle_type_name` on GNU systems.
- Document that string conversions assume non-null values.
- Start playing with C++20 _concepts._
- Sketch out concepts-based `PQconnectdbParams` support. (#343)
- Add missing link to "datatypes" documentation. (#346)
- Supports `to_string`, `stream_to`, etc. for `binarystring`. (#312)
- Fixed infinite recursion when using `std::optional` in `stream_to`. (#364)
- Home-rolled hex-escaping. Saves an allocation.
- Catch floating-point negative overflow in `check_cast`, not underflow.
- Bit more work on CMake build doc. (#318)
- Typo in `datatypes.md`: `nullness`, not `nullness_traits`. (#353)
- Fixed test names map in `tests/runner.cxx`. (#354)
- Integral `from_string` now accept leading whitespace, as in composite types.
- Experimental support basics for composite types. (#355)
- Use `stream_from` without knowing the number of fields. (#357)
- Global `size_buffer` function.
- `quote()` now works for always-null types without conversions defined.
- `std::nullopt` now converts to an SQL null.
- Skip quoting and escaping array/composite fields of "safe" types.
- New type trait: `is_unquoted_safe`.
- Forbid invalid specialisations of `query_value`.
- Fixed `mktemp` invocation that broke on FreeBSD.
- Avoid unneeded encode/decode step on more binary data.
- If `__cxa_demangle` fails, fall back on raw type name. (#361)
Changes in MySQL 5.7.32 (2020-10-19, General Availability)
Functionality Added or Changed
Bugs Fixed
Functionality Added or Changed
LOCK TABLES privilege checking for views was improved.
Bugs Fixed
InnoDB: A query that updated the clustered index of an internal temporary table returned an incorrect result. The modified pages of the clustered index were not added to the flush list resulting in lost changes when the modified pages were evicted from the buffer pool.
References: This issue is a regression of:
InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation on a large encrypted and compressed table failed with a Page decompress failed after reading from disk error. The decryption operation did not use the encryption block size used during encryption. Also, the encryption process did not consider compressed length, while the decryption process decrypts data by compressed length only.
InnoDB: A failure occurred during a concurrent update operation. The failure was due to an invalid previous record value.
InnoDB: The function used to process the SHOW ENGINE INNODB MUTEX statement was insufficiently isolated from other threads adding new mutexes concurrently.
InnoDB: The buffer control block structure (buf_block_t) was freed while reducing the size of the buffer pool, causing an assertion failure. The fix for this bug also backports important aspects of the fix for
InnoDB: In session started with START TRANSACTION WITH CONSISTENT SNAPSHOT, a range query returned a truncated result. The end range flag was not reset at the beginning of the index read resulting in an aborted read and missing rows.
References: This issue is a regression of:
InnoDB: A full-text phrase search raised an assertion failure.
Thanks to TXSQL (Tencent MySQL) for the contribution.
References: This issue is a regression of:
InnoDB: A long running statistics calculation operation on a large table blocked other operations requiring access to the table's statistics, causing those operations to fail. A new statistics calculation mutex was introduced, which permits concurrent access table statistics.
Thanks to Kamil Holubicki for the contribution.
InnoDB: Two connections attempted to use the same transaction handler object resulting in a stalled query.
Replication: When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the table must be emptied by writing a statement to the binary log to that effect. Previously, this was a DELETE statement, but it is now a TRUNCATE TABLE statement. A replica server also writes this statement to its own binary log when it shuts down and restarts. The statement is always logged in statement format, even if the binary logging format is set to ROW, and it is written even if read_only or super_read_only mode is set on the server.
Replication: When the system variable session_track_gtids was set to OWN_GTID on a multithreaded replica, the replica’s performance would degrade over time and begin to lag behind the master. The cause was the buildup of the GTIDs recorded by the replica’s worker threads at each transaction commit, which increased the time taken by the worker threads to insert new ones. Session state tracking is now disabled for worker threads on a multithreaded replica. Thanks to Facebook for the contribution.
Certain cases of successful LDAP authentication could cause the server to hang.
In bootstrapping mode, certain multiple-statement transactions could cause unexpected server behavior.
Sensitive LDAP authentication plugin system variables now display as asterisks when retrieved in SQL statements.
After the fix for
References: This issue is a regression of:
Some INSERT statements were not handled correctly.
Certain prepared statements could cause an unexpected server exit.
mysqlpump object validation included objects in excluded databases.
LDAP authentication plugins enforced CA verification incorrectly, which could result in use of an incorrect CA.
ORDER BY queries were not executed correctly when sort_buffer_size and max_sort_length were set to values which caused the internal limit on the maximum number of keys allowed per sort buffer to be set to 0.
A large number of nested arguments in full-text search query caused an error.
When explicit_defaults_for_timestamp was disabled and a NULL was inserted into a generated column declared as TIMESTAMP NOT NULL, the server would attempt to convert the inserted value to CURRENT_TIMESTAMP. Such an insertion is now rejected with ER_BAD_NULL_ERROR.
An assertion could be raised when the SQL layer passed incorrect information to InnoDB about the type of operation to be performed on a temporary table.
1.3.20
Released: October 12, 2020
orm
[orm] [bug]
An ArgumentError with more detail is now raised if the target parameter for Query.join() is set to an unmapped object. Prior to this change a less detailed AttributeError was raised. Pull request courtesy Ramon Williams.
[orm] [bug]
Fixed issue where using a loader option against a string attribute name that is not actually a mapped attribute, such as a plain Python descriptor, would raise an uninformative AttributeError; a descriptive error is now raised.
engine
[engine] [bug]
Fixed issue where a non-string object sent to SQLAlchemyError or a subclass, as occurs with some third party dialects, would fail to stringify correctly. Pull request courtesy Andrzej Bartosiński.
[engine] [bug]
Repaired a function-level import that was not using SQLAlchemy’s standard late-import system within the sqlalchemy.exc module.
sql
[sql] [bug]
Fixed issue where the pickle.dumps() operation against Over construct would produce a recursion overflow.
[sql] [bug]
Fixed bug where an error was not raised in the case where a column() were added to more than one table() at a time. This raised correctly for the Column and Table objects. An ArgumentError is now raised when this occurs.
postgresql
[postgresql] [usecase]
The psycopg2 dialect now support PostgreSQL multiple host connections, by passing host/port combinations to the query string. Pull request courtesy Ramon Williams.
See also
Specfiying multiple fallback hosts
[postgresql] [bug]
Adjusted the Comparator.any() and Comparator.all() methods to implement a straight “NOT” operation for negation, rather than negating the comparison operator.
[postgresql] [bug]
Fixed issue where the ENUM type would not consult the schema translate map when emitting a CREATE TYPE or DROP TYPE during the test to see if the type exists or not. Additionally, repaired an issue where if the same enum were encountered multiple times in a single DDL sequence, the “check” query would run repeatedly rather than relying upon a cached value.
mysql
[mysql] [usecase]
Adjusted the MySQL dialect to correctly parenthesize functional index expressions as accepted by MySQL 8. Pull request courtesy Ramon Williams.
[mysql] [bug]
The “skip_locked” keyword used with with_for_update() will emit a warning when used on MariaDB backends, and will then be ignored. This is a deprecated behavior that will raise in SQLAlchemy 1.4, as an application that requests “skip locked” is looking for a non-blocking operation which is not available on those backends.
[mysql] [bug]
Fixed bug where an UPDATE statement against a JOIN using MySQL multi-table format would fail to include the table prefix for the target table if the statement had no WHERE clause, as only the WHERE clause were scanned to detect a “multi table update” at that particular point. The target is now also scanned if it’s a JOIN to get the leftmost table as the primary table and the additional entries as additional FROM entries.
[mysql] [change]
Add new MySQL reserved words: cube, lateral added in MySQL 8.0.1 and 8.0.14, respectively; this indicates that these terms will be quoted if used as table or column identifier names.
mssql
[mssql] [bug]
Fixed issue where a SQLAlchemy connection URI for Azure DW with authentication=ActiveDirectoryIntegrated (and no username+password) was not constructing the ODBC connection string in a way that was acceptable to the Azure DW instance.
misc
[bug] [pool]
Fixed issue where the following pool parameters were not being propagated to the new pool created when Engine.dispose() were called: pre_ping, use_lifo. Additionally the recycle and reset_on_return parameter is now propagated for the AssertionPool class.
[bug] [associationproxy] [ext]
An informative error is now raised when attempting to use an association proxy element as a plain column expression to be SELECTed from or used in a SQL function; this use case is not currently supported.
[bug] [tests]
Fixed incompatibilities in the test suite when running against Pytest 6.x.
2.22.0
As announced in the 2.21.0 release notes, the experimental gRPC API v2 has been
removed.
[CHANGE] web: Remove APIv2.
[ENHANCEMENT] React UI: Implement missing TSDB head stats section.
[ENHANCEMENT] UI: Add Collapse all button to targets page.
[ENHANCEMENT] UI: Clarify alert state toggle via checkbox icon.
[ENHANCEMENT] Add rule_group_last_evaluation_samples and prometheus_tsdb_data_replay_duration_seconds metrics.
[ENHANCEMENT] Gracefully handle unknown WAL record types.
[ENHANCEMENT] Issue a warning for 64 bit systems running 32 bit binaries.
[BUGFIX] Adjust scrape timestamps to align them to the intended schedule, effectively reducing block size. Workaround for a regression in go1.14+.
[BUGFIX] promtool: Ensure alert rules are marked as restored in unit tests.
[BUGFIX] Eureka: Fix service discovery when compiled in 32-bit.
[BUGFIX] Don't do literal regex matching optimisation when case insensitive.
[BUGFIX] Fix classic UI sometimes running queries for instant query when in range query mode.
2.1.3 (2020-09-28)
* Removed old/unused appveyor config
* Remove old Rubies from CI & cross compile list
* Add Ruby 2.6 and 2.7 to the cross compile list
=== 5.37.0 (2020-10-01)
* Recognize more unsigned decimal/float types in the schema dumper (akimd, jeremyevans) (#1720)
* Add Postgres::PGRow::{Array,Hash}Row#op to the pg_row_ops extension if the pg_row extension is loaded (jeremyevans)
* Add Model#column_previously_was and #column_previously_changed? to the dirty plugin (jeremyevans)
* Raise Migrator::Error if attempting to migrate down to a version where there are necessary migration files missing (jeremyevans) (#1716)
Update Ruby on Rails 6.0 related packages to 6.0.3.4.
This is security fix for ruby-actionpack60.
## Rails 6.0.3.4 (October 07, 2020) ##
* [CVE-2020-8264] Prevent XSS in Actionable Exceptions
PostgreSQL 13 contains many new features and enhancements, including:
* Space savings and performance gains from de-duplication of B-tree index entries
* Improved performance for queries that use aggregates or partitioned tables
* Better query planning when using extended statistics
* Parallelized vacuuming of indexes
* Incremental sorting
1.4.3
bug
[bug] [batch] [sqlite]
Added support to drop named CHECK constraints that are specified as part of a column, rather than table wide. Previously, only constraints associated with the table were considered.
[bug] [mysql] [ops]
Fixed issue where the MySQL dialect would not correctly render the server default of a column in an alter operation, if the operation were programmatically generated from an autogenerate pass as it would not accommodate for the full structure of the DefaultClause construct.
[bug] [batch] [sqlite]
Fixed issue where the CAST applied to a JSON column when copying a SQLite table during batch mode would cause the data to be lost, as SQLite’s CAST with JSON appears to convert the data to the value “0”. The CAST is now skipped in a dialect-specific manner, including for JSON columns on SQLite. Pull request courtesy Sebastián Ramírez.
[bug] [commands]
The alembic current command no longer creates an alembic_version table in the database if one does not exist already, returning no version as the current version. This allows checking for migrations in parallel without introducing race conditions. Pull request courtesy Nikolay Edigaryev.
[bug] [batch]
Fixed issue where columns in a foreign-key referenced table would be replaced with null-type columns during a batch operation; while this did not generally have any side effects, it could theoretically impact a batch operation that also targets that table directly and also would interfere with future changes to the .append_column() method to disallow implicit replacement of columns.
[bug] [mssql]
Fixed issue where the mssql_drop_foreign_key=True flag on op.drop_column would lead to incorrect syntax error due to a typo in the SQL emitted, same typo was present in the test as well so it was not detected. Pull request courtesy Oleg Shigorin.
OpenLDAP 2.4.54
Fixed slapd delta-syncrepl to ignore delete ops on deleted entry
Fixed slapd delta-syncrepl to be fully serialized
Fixed slapd delta-syncrepl MOD on zero-length context entry
Fixed slapd sessionlog to use a TAVL tree
Fixed slapd syncrepl to be fully serialized
Fixed slapd syncrepl to call check_syncprov on fresh consumer
Fixed slapd syncrepl to propagate errors from overlay_entry_get_ov
Fixed slapd syncrepl to not create empty ADD ops
Fixed slapd syncrepl replace usage on single valued attrs
Fixed slapd-monitor fix monitor_back_register_database for empty suffix DB
Fixed slapo-accesslog normalizer for reqStart
Fixed slapo-accesslog to not generate new contextCSN on purge
Fixed slapo-syncprov contextCSN generation with empty suffix
TimescaleDB is an open-source database designed to make SQL scalable for
time-series data. It is engineered up from PostgreSQL and packaged as a
PostgreSQL extension, providing automatic partitioning across time and space
(partitioning key), as well as full SQL support.
WWW: https://github.com/timescale/timescaledb
pkgsrc changes: Adjust API_DEPENDS to 2.0. I don't have a specific
reason, but the previous 1.4 is so ancient that accepting it defies
the Principle of Least Astonishment.
Note that regression tests crash, but in the same way as 3.0.1.
3.0.1, when committed, passed, and I believe this is about proj.
Upstream changes: Bug fixes
2.21.0
This release is built with Go 1.15, which deprecates X.509 CommonName
in TLS certificates validation.
In the unlikely case that you use the gRPC API v2 (which is limited to TSDB
admin commands), please note that we will remove this experimental API in the
next minor release 2.22.
[CHANGE] Disable HTTP/2 because of concerns with the Go HTTP/2 client.
[CHANGE] PromQL: query_log_file path is now relative to the config file.
[CHANGE] Promtool: Replace the tsdb command line tool by a promtool tsdb subcommand.
[CHANGE] Rules: Label rule_group_iterations metric with group name.
[FEATURE] Eureka SD: New service discovery.
[FEATURE] Hetzner SD: New service discovery.
[FEATURE] Kubernetes SD: Support Kubernetes EndpointSlices.
[FEATURE] Scrape: Add per scrape-config targets limit.
[ENHANCEMENT] Support composite durations in PromQL, config and UI, e.g. 1h30m.
[ENHANCEMENT] DNS SD: Add SRV record target and port meta labels.
[ENHANCEMENT] Docker Swarm SD: Support tasks and service without published ports.
[ENHANCEMENT] PromQL: Reduce the amount of data queried by remote read when a subquery has an offset.
[ENHANCEMENT] Promtool: Add --time option to query instant command.
[ENHANCEMENT] UI: Respect the --web.page-title parameter in the React UI.
[ENHANCEMENT] UI: Add duration, labels, annotations to alerts page in the React UI.
[ENHANCEMENT] UI: Add duration on the React UI rules page, hide annotation and labels if empty.
[BUGFIX] API: Deduplicate series in /api/v1/series.
[BUGFIX] PromQL: Drop metric name in bool comparison between two instant vectors.
[BUGFIX] PromQL: Exit with an error when time parameters can't be parsed.
[BUGFIX] Remote read: Re-add accidentally removed tracing for remote-read requests.
[BUGFIX] Rules: Detect extra fields in rule files.
[BUGFIX] Rules: Disallow overwriting the metric name in the labels section of recording rules.
[BUGFIX] Rules: Keep evaluation timestamp across reloads.
[BUGFIX] Scrape: Do not stop scrapes in progress during reload.
[BUGFIX] TSDB: Fix chunks.HeadReadWriter: maxt of the files are not set error.
[BUGFIX] TSDB: Delete blocks atomically to prevent corruption when there is a panic/crash during deletion.
[BUGFIX] Triton SD: Fix a panic when triton_sd_config is nil.
[BUGFIX] UI: Fix react UI bug with series going on and off.
[BUGFIX] UI: Fix styling bug for target labels with special names in React UI.
[BUGFIX] Web: Stop CMUX and GRPC servers even with stale connections, preventing the server to stop on SIGTERM.
1.57 2020-09-18T06:57:48Z
- Fixed bug rt133358 t/016_mock_add_resultset_test.t fails (with older DBI)
1.56 2020-09-17T14:35:10Z
- The DBD::st module now supports the last_insert_id method
- Result sets with callbacks can now specify a last_insert_id
3.33.0-r1
Small performance improvement in string handling
apsw module exposes Cursor, Blob, and Backup types (APSW issue 273)
pkg-config is used to detect International Components for Unicode (ICU) sdk when the SQLite ICU extension <https://www.sqlite.org/src/artifact?ci=trunk&filename=ext/icu/README.txt>`___ is enabled. It falls back to icu-config as before..
Added constants:
SQLITE_OPEN_SUPER_JOURNAL
0.16.15
Make DateField accept valid date str.
Add QuerySet.select_for_update().
check default for not None on pydantic model creation
propagate default to pydantic model
Add QuerySet.select_related().
Add custom attribute name for Prefetch instruction.
Add db_constraint for RelationalField family.
Now requires c++17.
Headline:
Easier, faster, neater: the transaction classes now have a stream
method. You specify a query and the C++ types to which you want
the fields converted, and you get to iterate over the rows. And
thanks to C++14 structured bindings, you can read the fields
straight into separate local variables:
for (auto const [id, name]:
tx.stream<int, std::string_view>("SELECT id, name FROM thing"))
{
process(id, name);
}
For super-fast access to a field's text-format contents, convert
it to std::string_view. It'll give you an immediate reference
to the buffer containing the field. Beware though: the buffer
only holds that text for the one iteration. The next iteration
will overwrite it.
Full list of changes at:
https://github.com/jtv/libpqxx/blob/7.1.2/NEWS
2.3.9
Fix that broke several driver builds. Sorry
2.3.8
Add configure support for editline
SQLDriversW was ignoring user config
SQLDataSources Fix termination character
Fix for pooling seg fault
Make calling SQLSetStmtAttrW call the W function in the driver is its there
Try and fix race condition clearing system odbc.ini file
Remove trailing space from isql/iusql SQL
When setting connection attributes set before connect also check if the W entry poins can be used
Try calling the W error functions first if available in the driver
Add iconvperdriver configure option to allow calling unicode_setup in SQLAllocHandle
iconv handles was being lost when reusing pooled connection
Catch null copy in iniPropertyInsert
Fix some leaks
Update ruby-sequel to 5.36.0.
=== 5.36.0 (2020-09-01)
* Handle passing keyword arguments through class methods defined via
Plugins.def_dataset_method on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through when loading plugins on Ruby 2.7+
(jeremyevans)
* Handle passing keyword arguments through migrations when defining custom
Database methods that accept keywords on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through Dataset#query when using the
query extension on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through the association proxy when using
the association_proxies plugin on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through the class method to a method
defined in dataset_module on Ruby 2.7+ (adam12) (#1713)
* Stream result sets in the odbc adapter for better performance and lower
memory usage (sparrovv) (#1711)
* Add Postgres::JSONBOp#set_lax and #path_*_tz methods to the pg_json_ops
extension for new jsonb functions added in PostgreSQL 13 (jeremyevans)
* Add Dataset#with_ties on PostgreSQL 13+ and Microsoft SQL Server to
include rows with same order as final row (jeremyevans)
* Add a :current_schema option to Database#view_exists? (only defined on
Oracle) to look in the current schema instead of non-system schemas
(jeremyevans) (#1710)
* Recognize another disconnect error in the mysql and mysql2 adapters
(jeremyevans) (#1706)
Update ruby-ldap to 0.9.20.
pkgsrc change: remove redundant "ruby" in CATEGORIES.
Wed Jul 11 21:58:38 UTC 2018 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.20
* Added support of LDAP_OPT_X_TLS_NEWCTX. Thanks to Kouhei Sutou.
Mon Jun 20 14:30:52 UTC 2016 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.19
* Fixed parsing of LDIF with CR LF line separators (GH-38).
Thanks to doppelreim.
Fri Mar 4 11:17:21 UTC 2016 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.18
* backout issue32 to compile for ruby-1.8.x.
Thanks to SUENAGA Hiroki.
Fri Feb 6 08:51:09 UTC 2015 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.17
* Use ruby object to keep LDAP search result instead of libldap's data structure.
* Use macro Check_LDAPENTRY for assertion inside native extension codes.
* Remove assertion code from macro GET_LDAPENTRY_DATA.
Thanks to SUENAGA Hiroki.
Update ruby-moneta to 1.4.0.
1.4.0 (2020-08-23)
* Adapters::Mongo - drop support for moped gem (#182)
* Adapters::Redis - use #exists? where available (#189)
* Some reorganisation of code into more separate files (#177)
Update ruby-activeldap to 6.0.3.
## 6.0.3: 2020-08-17 {#release-6-0-3}
### Improvements
* Added support for `save(validate: false)`.
[GitHub#180][Reported by Kevin McCormack]
* jndi: Added support for follow referrals.
[GitHub#182][Patch by Kevin McCormack]
### Fixes
* Fixed a bug that sub base is ignored in DN specified by `new`.
[GitHub#185][Reported by Kevin McCormack]
### Thanks
* Kevin McCormack
Redis 6.0.8
===========
Upgrade urgency HIGH: Anyone who's using Redis 6.0.7 with Sentinel or
CONFIG REWRITE command is affected and should upgrade ASAP.
Bug fixes:
* CONFIG REWRITE after setting oom-score-adj-values either via CONFIG SET or
loading it from a config file, will generate a corrupt config file that will
cause Redis to fail to start
* Fix issue with redis-cli --pipe on MacOS
* Fix RESP3 response for HKEYS/HVALS on non-existing key
* Various small bug fixes
New features / Changes:
* Remove THP warning when set to madvise
* Allow EXEC with read commands on readonly replica in cluster
* Add masters/replicas options to redis-cli --cluster call command
Module API:
* Add RedisModule_ThreadSafeContextTryLock
1.3.19
orm
[orm] [usecase]
Adjusted the workings of the Mapper.all_orm_descriptors() accessor to represent the attributes in the order that they are located in a deterministic way, assuming the use of Python 3.6 or higher which maintains the sorting order of class attributes based on how they were declared. This sorting is not guaranteed to match the declared order of attributes in all cases however; see the method documentation for the exact scheme.
orm declarative
[usecase] [declarative] [orm]
The name of the virtual column used when using the AbstractConcreteBase and ConcreteBase classes can now be customized, to allow for models that have a column that is actually named type. Pull request courtesy Jesse-Bakker.
sql
[sql] [bug]
Repaired an issue where the “ORDER BY” clause rendering a label name rather than a complete expression, which is particularly important for SQL Server, would fail to occur if the expression were enclosed in a parenthesized grouping in some cases. This case has been added to test support. The change additionally adjusts the “automatically add ORDER BY columns when DISTINCT is present” behavior of ORM query, deprecated in 1.4, to more accurately detect column expressions that are already present.
[sql] [bug] [datatypes]
The LookupError message will now provide the user with up to four possible values that a column is constrained to via the Enum. Values longer than 11 characters will be truncated and replaced with ellipses. Pull request courtesy Ramon Williams.
[sql] [bug]
Fixed issue where the Connection.execution_options.schema_translate_map feature would not take effect when the Sequence.next_value() function function for a Sequence were used in the Column.server_default parameter and the create table DDL were emitted.
postgresql
[postgresql] [bug]
Fixed issue where the return type for the various RANGE comparison operators would itself be the same RANGE type rather than BOOLEAN, which would cause an undesirable result in the case that a TypeDecorator that defined result-processing behavior were in use. Pull request courtesy Jim Bosch.
mysql
[mysql] [usecase]
The MySQL dialect will render FROM DUAL for a SELECT statement that has no FROM clause but has a WHERE clause. This allows things like “SELECT 1 WHERE EXISTS (subquery)” kinds of queries to be used as well as other use cases.
[mysql] [bug]
Fixed an issue where CREATE TABLE statements were not specifying the COLLATE keyword correctly.
[mysql] [bug]
Added MariaDB code 1927 to the list of “disconnect” codes, as recent MariaDB versions apparently use this code when the database server was stopped.
sqlite
[sqlite] [bug] [mssql] [reflection]
Applied a sweep through all included dialects to ensure names that contain single or double quotes are properly escaped when querying system tables, for all Inspector methods that accept object names as an argument (e.g. table names, view names, etc). SQLite and MSSQL contained two quoting issues that were repaired.
mssql
[mssql] [bug] [sql]
Fixed bug where the mssql dialect incorrectly escaped object names that contained ‘]’ character(s).
misc
[usecase] [py3k]
Added a **kw argument to the DeclarativeMeta.__init__() method. This allows a class to support the PEP 487 metaclass hook __init_subclass__.
OpenLDAP 2.4.53
Added slapd syncrepl additional SYNC logging
Fixed slapd syncrepl segfault on NULL cookie on REFRESH
Fixed slapd syncrepl to use fresh connection on REFRESH fallback
Fixed slapo-ppolicy race condition for pwdFailureTime
Build
Require OpenSSL 1.0.2 or later
Fixed libldap compilation issue with broken C compilers
Redis 6.0.7
Upgrade urgency MODERATE: several bugs with moderate impact are fixed,
Specifically the first two listed below which cause protocol errors for clients.
Bug fixes:
* CONFIG SET could hung the client when arrives during RDB/ROF loading (When
processed after another command that was also rejected with -LOADING error)
* LPOS command when RANK is greater than matches responded wiht broken protocol
(negative multi-bulk count)
* UNLINK / Lazyfree for stream type key would have never do async freeing
* PERSIST should invalidate WATCH (Like EXPIRE does)
* EXEC with only read commands could have be rejected when OOM
* TLS: relax verification on CONFIG SET (Don't error if some configs are set
and tls isn't enabled)
* TLS: support cluster/replication without tls-port
* Systemd startup after network is online
* Redis-benchmark improvements
* Various small bug fixes
New features:
* Add oom-score-adj configuration option to control Linux OOM killer
* Show IO threads statistics and status in INFO output
* Add optional tls verification mode (see tls-auth-clients)
Module API:
* Add RedisModule_HoldString
* Add loaded keyspace event
* Fix RedisModuleEvent_LoadingProgress
* Fix RedisModuleEvent_MasterLinkChange hook missing on successful psync
* Fix missing RM_CLIENTINFO_FLAG_SSL
* Refactor redismodule.h for use with -fno-common / extern
2.8.1:
- fixed regression in 2.8 for members returned in AD auto-range search
- fixed regression in 2.8 for attribute error in restartable class
- try to use Crypto library if present for hashing NTLM password on python interpreter missing the MD4 OpenSSL algorithm
