Bugs Fixed:
- InnoDB: A 4GB tablespace file size limit on Windows 32-bit systems has
been removed. The limit was due to an incorrect calculation performed
while extending the tablespace. (Bug #28934351)
- Replication: The write sets extracted by MySQL Replication from
transactions when the transaction_write_set_extraction system variable
is enabled (which is the default) are extracted from primary keys,
unique keys, and foreign keys. They are used to detect dependencies
and conflicts between transactions. Previously, write sets involving
multi-column foreign keys were incorrectly identifying each column as
a separate foreign key. The issue has now been fixed and foreign key
write sets include all referenced key columns. (Bug #34095747, Bug
#34144531)
- Replication: When the --replicate-same-server-id option was used to
make the replica not skip events that have its own server ID, if the
log file was rotated, replication stopped with an error. The log
rotation event now checks and applies the current value of the option.
(Bug #89375, Bug #27492990)
- Under certain circumstances TRUNCATE performance_schema.accounts
caused duplicated counts in global_status.
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-39.html
Sponsored by: Netzkommune GmbH
PR: 265468
Bugs Fixed:
- InnoDB: A TRUNCATE TABLE operation failed to remove data dictionary entries for columns that were dropped using ALGORITHM=INSTANT.
- InnoDB: An incorrect nullable column calculation on tables with instantly added columns caused data to be interpreted incorrectly
- InnoDB: The read_2_bytes() function in the InnoDB sources, which reads bytes from the log buffer, returned a null pointer.
- Replication: The COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE column in the Performance Schema table replication_group_member_stats could persistently show transactions related to view change events (View_change_log_event) that had already been applied. These events are queued in the Group Replication applier channel but applied in the Group Replication recovery channel, causing a race condition that could result in the counter decrement being lost. The increment of the count now takes place at a more suitable point, and the counter for COUNT_TRANSACTIONS_REMOTE_IN_APPLIER_QUEUE is also now set to zero when the applier is not busy.
- Debug MySQL binaries can now be built using -0g and -fno-inline.
See full Changelog here: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html
Sponsored by: Netzkommune GmbH
Convert to ASCII and trim EOL whitespace. The scripts are now identical
across all PostgreSQL server versions we have in the ports.
Verified by: cksum(1)
ChangeLog:
https://www.mongodb.com/docs/manual/release-notes/5.0/#5.0.12---sep-05--2022
* Add new implicitlyCreateIndex and enforceUniquenessCheck to shardCollection
command
* Add new enforceUniqueness to refineCollectionShardKey command
* Add addl. activation condition for
interruptBeforeProcessingPrePostImageOriginatingOp fail point
* A retry of _configSvrReshardCollection can succeed causing
resharding_coordinator_recovers_abort_decision.js to fail
* A retry of _shardsvrReshardCollection can cause DuplicateKey error
(resharding_nonblocking_coordinator_rebuild.js)
PR: 266293
Reported by: ronald-lists@klop.ws (maintainer)
These ports reference the pkg-descr file of some other port and used
to get the WWW entry from that other port's file.
Reported by: dan@langille.org (Dan Langille)
Most USES use a colon for build/run(/test) suffixes. Change kde.mk,
qt.mk and pyqt.mk to do the same, and update all ports using that.
Document in CHANGES.
PR: 266034
Exp-run by: antoine
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D36349
Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
a) just using the pkg-descr from the parents
b) or had their own separate pkg-descr with custom WWW
Use WWW?= in parents when the child's WWW is different.
Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.
Approved by: portmgr (implicit)
