5.48.0 (2021-09-01)
* Make the unused_associations plugin association reflection tracking work
correctly when combining coverage runs (jeremyevans)
* Add Database#like_without_collate on MSSQL, to avoid using COLLATE on LIKE
arguments, which can significantly improve performance (jeremyevans)
* Add Model::Errors#full_message private method for easiest i18n support for
errors with multiple attributes (jeremyevans) (#1779)
Cross-platform TUI database management tool written in Rust.
Features:
- Cross-platform support (macOS, Windows, Linux)
- Multiple Database support (MySQL, PostgreSQL, SQLite)
- Intuitive keyboard only control
As of MySQL 5.7, installations created using --initialize no longer
have an empty root password; one is generated as part of the process
and marked expired. (This message is in part simply advice to read the
documentation. However, it's possible other downstream packagers use
--initialize-insecure instead, which retains the old empty password
approach, so this could be a pkgsrc-specific detail to consider.)
Version 1.21, 2021-09-02
* Crash tolerance
By default it is possible for an abrupt crash (e.g., power failure,
OS kernel panic, or application process crash) to corrupt the gdbm
database file. A new Linux-only mechanism enables applications to
recover the database state corresponding to the most recent
successful gdbm_sync() call before the crash. See the chapter 17
"Crash Tolerance" in the GDBM manual.
* New database file format: numsync
The new "numsync" database format is designed to better support
crash tolerance. To create a database in numsync format, the gdbm_open
(or gdbm_fd_open) function must be given the GDBM_NEWDB|GDBM_NUMSYNC
flags. The GDBM_NUMSYNC flag also takes effect when used together
with GDBM_WRCREAT, provided that the new file is created.
New function gdbm_convert() is provided for converting the databases
from standard GDBM format to numsync and vice versa.
The gdbmtool tool can also be used for converting databases between
these two formats.
* Changes in gdbmtool
** Fix string output in non-ASCII encodings
Printable multi-byte sequences are correctly represented on output.
This also fixes octal representation of unprintable characters.
** The filename variable
This variable supplies the name of database file for use in "open"
command, if the latter is called without arguments. If "open" is
called with the file name argument, the "filename" variable is
initialized to this value.
** The fd variable
If set, its value must be an open file descriptor referring to a
GDBM database file. The "open" command will use gdbm_fd_open
function to use this file. Upon closing the database, this
descriptor will be closed and the variable will be unset.
The file descriptor to use can also be supplied using the
-d (--db-descriptor) command line option.
** The format variable
Defines the format in which new databases will be created. Allowed
values are: "standard" (default) and "numsync".
** New commands: upgrade and downgrade
The "upgrade" command converts current database to the numsync
(extended) format. The "downgrade" command converts current database
to the standard format.
** New command: snapshot
The "snapshot" command is part of the new crash tolerance support.
Given the names of two snapshot files, it analyzes them and selects
the one to be used for database recovery. See the GDBM manual,
section 17.5 "Manual crash recovery" for a detailed discussion of its
use.
The release fixes continuous aggregate refresh for postgres 12.8 and
13.4, a crash with ALTER TABLE commands and a crash with continuous
aggregates with HAVING clause.
This release adds new experimental features since the 2.3.1 release:
- APIs for chunk manipulation across data nodes
- The time_bucket_ng function, a newer version of time_bucket
PostgreSQL 11 is deprecated and not supported with TimescaleDB 2.4.
OpenLDAP 2.5.7 Release (2021/08/18)
Fixed lloadd client state tracking
Fixed slapd bconfig to canonicalize structuralObjectclass
Fixed slapd-ldif duplicate controls response
Fixed slapd-mdb multival crash when attribute is missing an equality matchingrule
Fixed slapd-mdb compatibility with OpenLDAP 2.4 MDB databases
Fixed slapd-mdb idlexp maximum size handling
Fixed slapd-monitor number of ops executing with asynchronous backends
Fixed slapd-sql to add support for ppolicy attributes
Fixed slapd-sql to close transactions after bind and search
Fixed slapo-accesslog to make reqMod optional
Fixed slapo-ppolicy logging when pwdChangedTime attribute is not present
Documentation
slapd-mdb(5) note max idlexp size is 30, not 31
slapo-accesslog(5) note that reqMod is optional
Add ldapvc(1) man page
Add guide section on load balancer
Updated guide to document multiprovider as replacement for mirrormode
Updated guide to clarify slapd-mdb upgrade requirements
Updated guide to document removal of deprecated options from client tools
OpenLDAP 2.5.6 Release (2021/07/27)
Fixed libldap buffer overflow
Fixed libldap missing mutex unlock on connection alloc failure
Fixed lloadd cn=config olcBkLloadClientMaxPending setting
Fixed slapd multiple config defaults
Fixed slapd ipv6 addresses to work with tcp wrappers
Fixed slapo-syncprov delete of nonexistent sessionlog
Build
Fixed library symbol versioning on Solaris
Fixed compile warning in libldap/tpool.c
Fixed compile warning in libldap/tls_o.c
Contrib
Fixed ppm module for sysconfdir
Documentation
Updated guide to document multival, idlexp, and maxentrysize
OpenLDAP 2.5.5 Release (2021/06/03)
Added libldap LDAP_OPT_TCP_USER_TIMEOUT support
Added lloadd tcp-user-timeout support
Added slapd-asyncmeta tcp-user-timeout support
Added slapd-ldap tcp-user-timeout support
Added slapd-meta tcp-user-timeout support
Fixed incorrect control OIDs for AuthZ Identity
Fixed libldap typo in util-int.c
Fixed libldap double free of LDAP_OPT_DEFBASE
Fixed libldap better TLS1.3 cipher suite handling
Fixed lloadd multiple issues
Fixed slapd slap_op_time to avoid duplicates across restarts
Fixed slapd typo in daemon.c
Fixed slapd slapi compilation
Fixed slapd to handle empty DN in extended filters
Fixed slapd syncrepl searches with empty base
Fixed slapd syncrepl refresh on startup
Fixed slapd abort due to typo
Fixed slapd-asyncmeta quarantine handling
Fixed slapd-asyncmeta to have a default operations timeout
Fixed slapd-ldap quarantine handling
Fixed slapd-mdb deletion of context entry
Fixed slapd-mdb off-by-one affecting search scope
Fixed slapd-meta quarantine handling
Fixed slapo-accesslog to record reqNewDN for modRDN ops
Fixed slapo-pcache locking during expiration
Build
Fixed slappw-argon2 module installation
Contrib
Update ldapc++/ldaptcl to use configure.ac
Documentation
ldap_first_attribute(3) - Document ldap_get_attribute_ber
ldap_modify(3) - Delete non-existent mod_next parameter
OpenLDAP 2.5.4 Release (2021/04/29)
Initial release for "general use".
3.36.0-r1
Implemented Connection.serialize() and Connection.deserialize(). They turn a database into bytes, and bytes into a database respectively.
Allow any subclass of VFS to implement WAL, not just direct subclasses. (APSW issue 311)
Added constants:
SQLITE_FCNTL_EXTERNAL_READER, SQLITE_FCNTL_CKSM_FILE
Update Ruby on Rails 6.1 pacakges to 6.1.4.1.
Real changes are in Action Pack (www/ruby-actionpack61).
## Rails 6.1.4.1 (August 19, 2021) ##
* [CVE-2021-22942] Fix possible open redirect in Host Authorization middleware.
Specially crafted "X-Forwarded-Host" headers in combination with certain
"allowed host" formats can cause the Host Authorization middleware in Action
Pack to redirect users to a malicious website.
Update Ruby on Rails 6.0 pacakges to 6.0.4.1.
Real changes are in Action Pack (www/ruby-actionpack60).
## Rails 6.0.4.1 (August 19, 2021) ##
* [CVE-2021-22942] Fix possible open redirect in Host Authorization middleware.
Specially crafted "X-Forwarded-Host" headers in combination with certain
"allowed host" formats can cause the Host Authorization middleware in Action
Pack to redirect users to a malicious website.
PostgreSQL 13.4, 12.8, 11.13, 10.18, 9.6.23
Security Issues
CVE-2021-3677: Memory disclosure in certain queries
Versions Affected: 11 - 13.
A purpose-crafted query can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can complete this attack at will. The attack does not require the ability to create objects. If server settings include max_worker_processes=0, the known versions of this attack are infeasible. However, undiscovered variants of the attack may be independent of that setting.
Bug Fixes and Improvements
This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 13, but many affect all supported versions.
Some of these fixes include:
Completely disable TLS/SSL renegotiation. This was previously disabled, but the server would still execute a client-initiated renegotiation request.
Restore the Portal-level snapshot after COMMIT or ROLLBACK within a procedure. This change fixes cases where an attempt to fetch a toasted value immediately after COMMIT/ROLLBACK would fail with errors like "no known snapshots" or "missing chunk number 0 for toast value".
Avoid misbehavior when persisting the output of a cursor that's reading a volatile query.
Reject cases where a query in WITH rewrites to just NOTIFY, which would cause a crash.
Several corner-case fixes for numeric types.
ALTER EXTENSION now locks the extension when adding or removing a member object.
The "enabled" status is now copied when a partitioned table's triggers are cloned to a new partition.
Avoid alias conflicts in queries generated for REFRESH MATERIALIZED VIEW CONCURRENTLY. This command failed on materialized views containing columns with certain names, notably mv and newdata.
Disallow whole-row variables in GENERATED expressions.
Several fixes for DROP OWNED BY behavior in relation to row-level security (RLS) policies.
Re-allow old-style Windows locale names in CREATE COLLATION commands.
walsenders now show their latest replication command in pg_stat_activity, instead of just showing the latest SQL command.
pg_settings.pending_restart now shows as true when a pertinent entry in postgresql.conf is removed.
On 64-bit Windows, allow the effective value of work_mem * hash_mem_multiplier to exceed 2GB.
Update minimum recovery point when WAL replay of a transaction abort record causes file truncation.
Advance oldest-required-WAL-segment horizon properly after a replication slot is invalidated. This fixes an issue where the server's WAL storage could run out of space.
Improve progress reporting for the sort phase of a parallel B-tree index build.
Fix assorted crash cases in logical replication of partitioned-table updates and when firing AFTER triggers of partitioned tables.
Prevent infinite loops in SP-GiST index insertion.
Ensure that SP-GiST index insertion can be terminated by a query cancel request.
In psql and other client programs, avoid overrunning the ends of strings when dealing with invalidly-encoded data.
Fix pg_dump to correctly handle triggers on partitioned tables whose enabled status is different from their parent triggers' status.
Avoid "invalid creation date in header" warnings when running pg_restore on a file created in a different time zone.
pg_upgrade now carries forward the old installation's oldestXID value and no longer forces an anti-wraparound VACUUM."
Extend pg_upgrade to detect and warn about extensions that should be upgraded.
Fix contrib/postgres_fdw to better work with generated columns, so long as a generated column in a foreign table represents a generated column in the remote table.
5.47.0 (2021-08-01)
* Make the unused_associations plugin track access to association
reflections to determine whether associations are used (jeremyevans)
* Support :db option for join tables in {many,one}_through_many to use a
separate query for each join table (jeremyevans)
* Support :join_table_db option for many_to_many/one_through_one
associations, to use a separate query for the join table (jeremyevans)
* Support :allow_eager_graph and :allow_filtering_by association options
(jeremyevans)
* Add Database#rename_tables on MySQL, for renaming multiple tables in a
single call (nick96) (#1774)
* Support Dataset#returning on SQLite 3.35+ (jeremyevans)
5.46.0 (2021-07-01)
* Add unused_associations plugin, for determining which associations and
association methods are not used (jeremyevans)
* Make nil :setter/:adder/:remover/:clearer association options not create
related methods (jeremyevans)
Issues fixed in 4.2.15:
SERVER-57476: Operation may block on prepare conflict while holding oplog slot, stalling replication indefinitely
SERVER-56779: Do not use the collection distributed lock for chunk merges
SERVER-56240: Turn on checkpointing for the keystore Data Store
SERVER-56054: Change minThreads value for replication writer thread pool to 0
SERVER-47699: Change yield type used by range deleter from YIELD_MANUAL to YIELD_AUTO
mongo-c-driver 1.17.7
Announcing 1.17.7 of libbson and libmongoc, the libraries constituting the MongoDB C Driver.
libbson
It is my pleasure to announce libbson 1.17.7.
No changes since 1.17.6; release to keep pace with libmongoc's version.
libmongoc
It is my pleasure to announce the MongoDB C Driver 1.17.7.
Print correct error message when DNS resolution fails
Mix time to avoid duplicate RAND_bytes for the same PIDs
v0.24.0
Changes
Drop support for Python 3.5
Add support for Python 3.10
Add support for asynchronous iterables to copy_records_to_table()
Add support for coroutine functions as listener callbacks
Add support for sslcert, sslkey and sslrootcert parameters to DSN
Add copy_ wrappers to Pool
Add issubset and issuperset methods to the Range type
Fixes
Break connection internal circular reference
Make Server Version Extraction More Flexible
Notable Items
InnoDB
* InnoDB no longer acquires advisory file locks by default (MDEV-24393)
* Encryption: Automatically disable key rotation checks for
file_key_management plugin (MDEV-14180)
* Some fixes from MySQL 5.7.35 (MDEV-26205)
* Fixed scrubbing on AIX (MDEV-26110)
* buf_pool.flush_list corrupted by buffer pool resizing or
ROW_FORMAT=COMPRESSED (MDEV-26200)
Optimizer
* A query that uses ORDER BY .. LIMIT clause and "Range checked for each
record optimization" could produce incorrect results under some
circumstances (MDEV-25858)
* Queries that have more than 32 equality conditions comparing columns
of different tables ("tableX.colX=tableY.colY) could cause a stack
overrun in the query optimizer (MDEV-17783, MDEV-23937)
* "Condition pushdown into derived table" optimization cannot be applied
if the expression being pushed refers to a derived table column which
is computed from expression that has a stored function call, @session
variable reference, or other similar construct. The fix for MDEV-25969
makes it so that only the problematic part of the condition is not
pushed. The rest of the condition is now pushed. (MDEV-25969)
* A query with window function on the left side of the subquery could
cause a crash. (MDEV-25630)
* Fixed the issue fixed in MySQL Bug #76803: DML or locking SELECT
statements that use outer joins could produce this warning in the
error log: [ERROR] InnoDB: Unlock row could not find a 3 mode lock on
the record. (MDEV-26106)
Security
* Fixes for the following security vulnerabilities:
* CVE-2021-2372
* CVE-2021-2389
Notable Items
InnoDB
* InnoDB no longer acquires advisory file locks by default (MDEV-24393)
* Encryption: Automatically disable key rotation checks for
file_key_management plugin (MDEV-14180)
* Some fixes from MySQL 5.7.35 (MDEV-26205)
* Fixed scrubbing on AIX (MDEV-26110)
* Improved page flushing performance (MDEV-25954, MDEV-25948,
MDEV-25801, MDEV-25113, MDEV-26004)
Optimizer
* A query that uses ORDER BY .. LIMIT clause and "Range checked for each
record optimization" could produce incorrect results under some
circumstances (MDEV-25858)
* Queries that have more than 32 equality conditions comparing columns
of different tables ("tableX.colX=tableY.colY) could cause a stack
overrun in the query optimizer (MDEV-17783, MDEV-23937)
* "Condition pushdown into derived table" optimization cannot be applied
if the expression being pushed refers to a derived table column which
is computed from expression that has a stored function call, @session
variable reference, or other similar construct. The fix for MDEV-25969
makes it so that only the problematic part of the condition is not
pushed. The rest of the condition is now pushed. (MDEV-25969)
* A query with window function on the left side of the subquery could
cause a crash. (MDEV-25630)
* Fixed the issue fixed in MySQL Bug #76803: DML or locking SELECT
statements that use outer joins could produce this warning in the
error log: [ERROR] InnoDB: Unlock row could not find a 3 mode lock on
the record. (MDEV-26106)
Security
* Fixes for the following security vulnerabilities:
* CVE-2021-2372
* CVE-2021-2389
