The MonetDB team at MonetDB Solutions BV is pleased to announce the Sep2022-SP3 bugfix release of the MonetDB suite of programs.
More information about MonetDB can be found on our website at https://www.monetdb.org/.
For details on this release, please see the release notes at https://www.monetdb.org/release-notes/sep2022/.
As usual, the download location is https://www.monetdb.org/downloads/.
### Client Package
- If the number of rows in mclient is set to 0 (using either --rows=0 option or \r0 on the mclient command line), the internal pager is used and it then uses the height of the terminal window.
### MonetDB Common
- Warnings and informational messages are now sent to stdout instead of stderr, which means that monetdbd will now log them with the tag MSG instead of ERR.
- Fixed parsing of the BBP.dir file when BAT ids grow larger than 2**24 (i.e. 100000000 in octal).
- Fixed yet another occurrence of a missing .tailN file. This one could happen if a string bat was appended to in stages so that between appends the column was committed. If an append caused both a realloc of the tail heap because it was getting longer and a realloc because it got wider, the file might get removed before the GDK level commit happened.
- When processing the WAL, if a to-be-destroyed object cannot be found, don't stop, but keep processing the rest of the WAL.
- A race condition was fixed where certain write-ahead log messages could get intermingled, resulting in a corrupted WAL file.
- If opening of a file failed when it was supposed to get memory mapped, an incorrect value was returned to indicate the failure, causing crashes later on. This has been fixed.
- A race condition was fixed that could result in a missing tail file for a string bat (i.e. a file with .tail1, .tail2, or .tail4 extension).
- When saving a bat failed for some reason during a low-level commit, this was logged in the log file, but the error was then subsequently ignored, possibly leading to files that are too short or even missing.
- The write-ahead log (WAL) is now rotated a bit more efficiently by doing multiple log files in one go (i.e. in one low-level transaction).
### MonetDB5 Server
- Client connections are cleaned up better so that we get fewer instances of clients that cannot connect.
### SQL Frontend
- Fixed a regression introduced in the previous build: when a table is dropped in the same transaction where it was created, the data wasn't removed from disk.
- When creating a hot snapshot, allow other clients to proceed, even with updating queries.
- Increased the size of a variable counting the number of changes made to the database (e.g. in case more than 2 billion rows are added to a table).
- Improved cleanup after failures such as failed memory allocations.
- An insert into a table from which a column was dropped in a parallel transaction was incorrectly not flagged as a transaction conflict.
- Fix bug where boolean NULLs were not recognized by COPY BINARY INTO
### Bug Fixes
- [7360](https://github.com/MonetDB/MonetDB/issues/7360): Aggregates returning string crash
- [7361](https://github.com/MonetDB/MonetDB/issues/7361): Table data is lost on DB restart, but only when a table has 2147483647 or more rows.