Age | Commit message (Collapse) | Author | Files | Lines |
|
Support for Alpha was removed in 2014. This removed the spinlock and
memory barrier implementations, meaning Postgresql on Alpha no longer
compiles cleanly with the default options. According to the commit
message the code was "unlikely to currently work correctly".
Enthusiasts may wish to re-add Alpha support, but it should likely
only be done with proper testing to avoid data loss in the case someone
uses it.
|
|
Version 3.11.4 fixes a bug where a MongoClient would mistakenly attempt to
create minPoolSize connections to arbiter nodes (`PYTHON-2634`_).
|
|
5.44.0 (2021-05-01)
* Add concurrent_eager_loading plugin, for eager loading multiple
associations concurrently using separate threads (jeremyevans)
* Support :weeks as a interval unit in the date_arithmetic extension
(jeremyevans) (#1759)
* Raise an exception if an interval hash with an unsupported key is passed
in the date_arithmetic extension (jeremyevans) (#1759)
* Support dropping non-composite unique constraints on SQLite (jeremyevans)
(#1755)
|
|
================================================================================
Redis 6.2.3 Released Mon May 3 19:00:00 IST 2021
================================================================================
Upgrade urgency: SECURITY, Contains fixes to security issues that affect
authenticated client connections. LOW otherwise.
Integer overflow in STRALGO LCS command (CVE-2021-29477):
An integer overflow bug in Redis version 6.0 or newer could be exploited using
the STRALGO LCS command to corrupt the heap and potentially result in remote
code execution. The integer overflow bug exists in all versions of Redis
starting with 6.0.
Integer overflow in COPY command for large intsets (CVE-2021-29478):
An integer overflow bug in Redis 6.2 could be exploited to corrupt the heap and
potentially result with remote code execution. The vulnerability involves
changing the default set-max-intset-entries configuration value, creating a
large set key that consists of integer values and using the COPY command to
duplicate it. The integer overflow bug exists in all versions of Redis starting
with 2.6, where it could result with a corrupted RDB or DUMP payload, but not
exploited through COPY (which did not exist before 6.2).
Bug fixes that are only applicable to previous releases of Redis 6.2:
* Fix memory leak in moduleDefragGlobals
* Fix memory leak when doing lazy freeing client tracking table
* Block abusive replicas from sending command that could assert and crash redis
Other bug fixes:
* Use a monotonic clock to check for Lua script timeout
* redis-cli: Do not use unix socket when we got redirected in cluster mode
Modules:
* Fix RM_GetClusterNodeInfo() to correctly populate master id
|
|
|
|
Now it should be more obvious when a package needs it as a dependency,
as it will fail loudly if it isn't declared as a tool.
While here, some duplicate dependencies on itstool were removed from the
MATE packages
|
|
|
|
Based on a diff provided by Mustafa Dogan.
4.2.1 and 4.2.2 are bugfix releases.
4.2 contains new features and enhancements, including:
Some items in the configuration file pgpool.conf are vastly
enhanced for easier configuration and administration.
Implement logging_collector for easier log management.
Implement log_disconnections to collect disconnection logs.
Implement pg_enc and pg_md5 to allow to register multiple
passwords at once.
Allow to show statistics of health check by using SHOW
POOL_HEALTH_CHECK_STATS command, and also allow to show statistics
of issued SQL by using SHOW POOL_BACKEND_STATS command.
New PCP command pcp_reload_config is added.
Now it is possible to omit write_function_list and
read_only_function_list by looking at system catalog information.
Add new clustering mode snapshot_isolation_mode which guarantees
not only data modifications to multiple PostgreSQL but read
consistency.
Support LDAP authentication between clients and Pgpool-II.
Add ssl_crl_file and ssl_passphrase_command to SSL configuration.
Import PostgreSQL 13's SQL parser.
|
|
Uses removed p5-Net-Google.
|
|
New high-availability system (experimental)
Major performance improvements
Bug fixes
support for PostgreSQL 13
|
|
Major Features
Add distributed restore point functionality
SkipScan to speed up SELECT DISTINCT
Bugfixes
Refactor and harden size and stats functions
Reduce memory usage for distributed inserts
Fix extremely slow multi-node order by queries
Fix chunk index column name mapping
Keep Append pathkeys in ChunkAppend
|
|
Redis 6.2.2
===========
Upgrade urgency: HIGH, if you're using ACL and pub/sub, CONFIG REWRITE, or
suffering from performance regression. see below.
Bug fixes for regressions in previous releases of Redis 6.2:
* Fix BGSAVE, AOFRW, and replication slowdown due to child reporting CoW
* Fix short busy loop when timer event is about to fire
* Fix default user, overwritten and reset users losing pubsub channel permissions
* Fix config rewrite with an empty `save` config resulsing in default `save` values
* Fix not starting on alpine/libmusl without IPv6
* Fix issues with propagation and MULTI/EXEC in modules
Several issues around nested calls and thread safe contexts
Bug fixes that are only applicable to previous releases of Redis 6.2:
* ACL Pub/Sub channels permission handling for save/load scenario
* Fix early rejection of PUBLISH inside MULTI-EXEC transaction
* Fix missing SLOWLOG records for blocked commands
* Allow RESET command during busy scripts
* Fix some error replies were not counted on stats
Bug fixes:
* Add a timeout mechanism for replicas stuck in fullsync
* Process HELLO command even if the default user has no permissions
* Client issuing a long running script and using a pipeline, got disconnected
* Fix script kill to work also on scripts that use `pcall`
* Fix list-compress-depth may compress more node than required
* Fix redis-cli handling of rediss:// URL scheme
* Cluster: Skip unnecessary check which may prevent failure detection
* Cluster: Fix hang manual failover when replica just started
* Sentinel: Fix info-refresh time field before sentinel get first response
* Sentinel: Fix possible crash on failed connection attempt
* Systemd: Send the readiness notification when a replica is ready to accept connections
Command behavior changes:
* ZADD: fix wrong reply when INCR used with GT/LT which blocked the update
It was responding with the incremented value rather than nil
* XAUTOCLAIM: fix response to return the next available id as the cursor
Previous behavior was retuning the last one which was already scanned
* XAUTOCLAIM: fix JUSTID to prevent incrementing delivery_count
New config options:
* Add cluster-allow-replica-migration config option
* Add replica-announced config option
* Add support for plaintext clients in TLS cluster
* Add support for reading encrypted keyfiles
Improvements:
* Fix performance regression in BRPOP on Redis 6.0
* Avoid adding slowlog entries for config with sensitive data
* Improve redis-cli non-binary safe string handling
* Optimize CLUSTER SLOTS reply
* Handle remaining fsync errors
Info fields and introspection changes:
* Strip % sign from current_fork_perc info field
* Fix RSS memory info on FreeBSD
* Fix client_recent_max_input/output_buffer in 'INFO CLIENTS' when all clients drop
* Fix invalid master_link_down_since_seconds in info replication
Platform and deployment-related changes:
* Fix FreeBSD <12.x builds
Modules:
* Add macros for RedisModule_log logging levels
* Add RedisModule_GetAbsExpire / RedisModule_SetAbsExpire
* Add a module type for key space notification
* Set module eviction context flag only in masters
* Fix unusable RedisModule_IsAOFClient API
* Fix missing EXEC on modules propagation after failed EVAL execution
* Fix edge-case when a module client is unblocked
|
|
Changes in MySQL 5.7.34 (2021-04-20, General Availability)
Configuration Notes
The CMAKE_BUILD_TYPE CMake option now supports a Release build type, which is like the RelWithDebInfo build type but omits debugging information to reduce the build size.
Packaging Notes
The bundled libedit library was upgraded to version 20190324-3.1.
Binary packages that include curl rather than linking to the system curl library have been upgraded to use curl 7.74.0.
Security Notes
The linked OpenSSL library for MySQL Server has been updated to version 1.1.1k. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html.
Functionality Added or Changed
Microsoft Windows: The named_pipe_full_access_group system variable now defaults to an empty string (''), making named pipe connections secure. Previously, '*everyone*' was the default value. A valid Windows local group name may be substituted.
Bugs Fixed
InnoDB: The introduction of sharded rw_lock_stats counters in MySQL 5.7 caused a regression in CPU cache efficiency. To address this issue in MySQL 5.7, the sharding method was changed. For optimal performance, the rw_lock_stats counter is removed in MySQL 8.0.
InnoDB: A delete operation on a parent table that initiated a cascading update on a child table with an indexed virtual column and indexed foreign key constraint column caused a virtual column corruption.
InnoDB: An adaptive hash index (AHI) latch was held in shared mode by a thread truncating a large table, causing mutex waits for other threads. The AHI latch was not required and has been removed.
InnoDB: The open and close sequence for table share instances (m_share objects) and dictionary table instances was modified to prevent accessing old m_share objects that could point to stale dictionary indexes.
Thanks to Yuxiang Jiang for the contribution.
InnoDB: An online ALTER TABLE operation failed with an “Incorrect key file for table” error due to an unnecessary encryption status check that was performed when reading online DDL row logs.
Replication: If all previous binary log files were purged at startup because their retention period had expired, the new binary log file contained an empty Previous_gtids event, which could cause errors in replication. The order of initialization has now been changed so that previous binary log files are only purged after the previous GTID set has been written to the new binary log file that is created at startup.
Replication: An assertion was raised in debug builds relating to lost GTIDs if binary log files were removed at startup because their retention period had expired.
Replication: A deadlock could occur if the binary log file was rotated while system variables were being updated and read by different clients.
Replication: The output of a SHOW PROCESSLIST statement for a replica’s SQL thread sometimes showed the last query as currently being applied when the replica was actually caught up.
A query string was displayed before it had been rewritten.
For builds compiled using the libedit library, if the mysql client was invoked with the --default-character-set=utf8 option, libedit rejected input of multibyte characters.
On Windows, large result sets could cause the mysql client to exit unexpectedly.
Improper locking on an internal queue could cause mysqlpump to exit unexpectedly.
It is now possible to use START REPLICA SQL_THREAD and STOP REPLICA SQL_THREAD statements for the group_replication_applier channel when Group Replication is stopped. This enables an operator to apply any remaining unapplied transactions on a server that left the group, without having to rejoin the server to the group.
When the mysql client was used in batch mode, its parser could be confused by USE followed by DROP DATABASE when the USE database name was quoted.
While optimizing the ORDER BY clause of a subquery there was a possibility of cleaning up a subquery tree referenced in the outer SELECT, which could lead to a premature exit.
A malformed name in the mysql.func system table could cause unexpected server behavior.
Sessions could disable their own auditing.
Mishandling of stored program local variables could lead to unexpected server behavior.
Uninstalling a plugin could affect subsequent execution of prepared statements.
|
|
|
|
|
|
|
|
|
|
|
|
version 3.35.5:
Fix defects in the new ALTER TABLE DROP COLUMN feature that could corrupt the database file.
Fix an obscure query optimizer problem that might cause an incorrect query result.
|
|
|
|
3.35.4-r1
Updates for SQLite download url (the year is part of the urls).
Added enable flag for built-in SQL math functions, and enable it by default with –enable-all-extensions.
Use the newer buffer API for Python 3 (old API removed in Python 3.10).
|
|
0.48.1:
Bug fixes
|
|
2.3.0:
Unknown changes
|
|
|
|
5.43.0 (2021-04-01)
* Add column_encryption plugin, for encrypting column values (jeremyevans)
|
|
Real changes are in devel/devel/ruby-activestorage61 only.
## Rails 6.1.3.1 (March 26, 2021) ##
* Marcel is upgraded to version 1.0.0 to avoid a dependency on GPL-licensed
mime types data.
*George Claghorn*
|
|
Real changes are in devel/ruby-activestorage60 only.
## Rails 6.0.3.6 (March 26, 2021) ##
* Marcel is upgraded to version 1.0.0 to avoid a dependency on GPL-licensed
mime types data.
*George Claghorn*
|
|
Real changes are in devel/ruby-activestorage52 only.
## Rails 5.2.5 (March 26, 2021) ##
* Marcel is upgraded to version 1.0.0 to avoid a dependency on GPL-licensed
mime types data.
*George Claghorn*
* The Poppler PDF previewer renders a preview image using the original
document's crop box rather than its media box, hiding print margins. This
matches the behavior of the MuPDF previewer.
*Vincent Robert*
|
|
|
|
10 months worth of updates.
|
|
|
|
|
|
|
|
This uses the upstream commit hash that will likely become version 0.1.2
but that is not formally release so call this 0.1.1 with PKGREVISION 2.
|
|
Prometheus is now built and supporting Go 1.16.
Note that from this release Prometheus is using Alertmanager v2 by default.
[CHANGE] Alerting: Using Alertmanager v2 API by default.
[CHANGE] Prometheus/Promtool: As agreed on dev summit, binaries are now printing help and usage to stdout instead of stderr.
[FEATURE] Remote: Add support for AWS SigV4 auth method for remote_write.
[FEATURE] Scaleway Discovery: Add Scaleway Service Discovery.
[FEATURE] PromQL: Allow negative offsets. Behind --enable-feature=promql-negative-offset flag.
[FEATURE] experimental Exemplars: Add in-memory storage for exemplars. Behind --enable-feature=exemplar-storage flag.
[FEATURE] UI: Add advanced auto-completion, syntax highlighting and linting to graph page query input.
[ENHANCEMENT] Digital Ocean Discovery: Add __meta_digitalocean_image label.
[ENHANCEMENT] PromQL: Add last_over_time, sgn, clamp functions.
[ENHANCEMENT] Scrape: Add support for specifying type of Authorization header credentials with Bearer by default.
[ENHANCEMENT] Scrape: Add follow_redirects option to scrape configuration.
[ENHANCEMENT] Remote: Allow retries on HTTP 429 response code for remote_write. Disabled by default. See configuration docs for details.
[ENHANCEMENT] Remote: Allow configuring custom headers for remote_read. See configuration docs for details.
[ENHANCEMENT] UI: Hitting Enter now triggers new query.
[ENHANCEMENT] UI: Better handling of long rule and names on the /rules and /targets pages.
[ENHANCEMENT] UI: Add collapse/expand all button on the /targets page.
[BUGFIX] TSDB: Eager deletion of removable blocks on every compaction, saving disk peak space usage.
[BUGFIX] PromQL: Fix parser support for special characters.
[BUGFIX] Rules: Update rule health for append/commit fails.
|
|
This adds support for TimescaleDB 2.1.
|
|
This release add support for PostgreSQL major version 13.
|
|
3.35.4
Fix a defect in the query planner optimization identified by item 8b above.
Fix a defect in the new RETURNING syntax.
Fix the new RETURNING feature so that it raises an error if one of the terms in the RETURNING clause references a unknown table, instead of silently ignoring that error.
Fix an assertion associated with aggregate function processing that was incorrectly triggered by the push-down optimization.
|
|
The previous change for CVE-2016-2121 installed a configuration file that could
not be read by the default redis user. Bump PKGREVISION.
|
|
|
|
Apparently, minimum version of dependency to php-* packages
insists that it is now incompatible to php56.
Should be solve a problem of pbulk.
|
|
This release incorporates the following changes:
* Add support for Postgres 13
* Add provisional support for Postgres 14
* Upgrade Jquery library to 3.4.1 (Nirgal)
* Allow users to see group owned databases when using "owned only"
* Fix bug where sorting on selects dumped you to the table screen (MichaMEG)
* This release drops support for PHP 7.1
* This will be the last release to support PHP 7.
Release 7.12.1 incorporated the following changes:
* Fix a number of issues related to changes in Postgres 12.
* Fix an issue with truncation of long multibyte strings
* Removal of broken tree branches from table/view browse option
* Properly escape identifiers when browsing tables/views/schemas
* Add support for granting USAGE on sequences
Release 7.12.0 incorporated the following changes:
* PHP 7.1 is now the default version for development
* Added support for all current versions of PostgreSQL (including 12)
* Updated some internal libraries, fixed additional bugs, and merged in patches
Finally, release 5.6 added support for all recent versions of Postgres (at
least 9.3 - 12devel). It also fixed a number of minor bugs and included several
language fixes.
|
|
changes in version 3.35.3
Enhance the OP_OpenDup opcode of the bytecode engine so that it works even if the cursor being duplicated itself came from OP_OpenDup. Fix for ticket bb8a9fd4a9b7fce5. This problem only came to light due to the recent MATERIALIZED hint enhancement.
When materializing correlated common table expressions, do so separately for each use case, as that is required for correctness. This fixes a problem that was introduced by the MATERIALIZED hint enhancement.
Fix a problem in the filename normalizer of the unix VFS.
Fix the "box" output mode in the CLI so that it works with statements that returns one or more rows of zero columns (such as PRAGMA incremental_vacuum). Forum post afbbcb5b72.
Improvements to error messages generated by faulty common table expressions. Forum post aa5a0431c99e.
Fix some incorrect assert() statements.
Fix to the SELECT statement syntax diagram so that the FROM clause syntax is shown correctly. Forum post 9ed02582fe.
Fix the EBCDIC character classifier so that it understands newlines as whitespace. Forum post 58540ce22dcd.
Improvements the xBestIndex method in the implementation of the (unsupported) wholenumber virtual table extension so that it does a better job of convincing the query planner to avoid trying to materialize a table with an infinite number of rows.
|
|
php-json is bundled in lang/php80 pacakge.
|
|
|
|
|
|
==============================
Release Notes for Samba 4.13.7
March 24, 2021
==============================
This is a follow-up release to depend on the correct ldb version. This is only
needed when building against a system ldb library.
This is a security release in order to address the following defects:
o CVE-2020-27840: Heap corruption via crafted DN strings.
o CVE-2021-20277: Out of bounds read in AD DC LDAP server.
=======
Details
=======
o CVE-2020-27840:
An anonymous attacker can crash the Samba AD DC LDAP server by sending easily
crafted DNs as part of a bind request. More serious heap corruption is likely
also possible.
o CVE-2021-20277:
User-controlled LDAP filter strings against the AD DC LDAP server may crash
the LDAP server.
For more details, please refer to the security advisories.
Changes since 4.13.6
--------------------
o Release with dependency on ldb version 2.2.1.
|
|
Sat Dec 26 2020 version 0.999991 released
* update to compile with newer Ruby releases
* report larger width for SQL_(DECIMAL|NUMERIC) columns
|
|
3.7.0 (2021-03-15)
* Fix typo in DESCR.
* Add license to gemspec.
|
|
3.14.4
This release contains an important fix for a regression introduced by commit
ebe3ad5, which affected the way model instances are converted to parameters for
use in expressions within a query. The bug could manifest when code uses model
instances as parameters in expressions against fields that are not
foreign-keys.
|