The MonetDB team at MonetDB Solutions BV is pleased to announce the Jun2023-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/jun2023/.
As usual, the download location is https://www.monetdb.org/downloads/.
### MonetDB Common
- Fixed a regression where after a while the write-ahead log files weren't being rotated, meaning from some point onwards, the newest file just kept on growing.
- When saving the SQL catalog during a low-level commit, we should only save the part of the catalog that corresponds to the part of the write-ahead log that has been processed. What we did was save more, which resulted in the catalog containing references to tables and columns whose disk presence is otherwise only in the write-ahead log.
- A bug was fixed where the administration of which bats were in use was interpreted incorrectly during startup, causing problems later. One symptom that has been observed was failure to startup with a message that the catalog tables could not be loaded.
### SQL Frontend
- Added a missing interface function sys.timestamp_to_str with a TIMESTAMP (as opposed to TIMESTAMP WITH TIME ZONE) argument. The missing interface caused error messages being produced when the function was called with a TIMESTAMP argument, although it did give the correct result.
### Bug Fixes
- [7300](https://github.com/MonetDB/MonetDB/issues/7300): Implement missing standard SQL DATE and TIMESTAMP functions
- [7324](https://github.com/MonetDB/MonetDB/issues/7324): string_distance('method',str1, str2) as a generic distance function
- [7409](https://github.com/MonetDB/MonetDB/issues/7409): Numpy table returning UDFs with variadic arguments
- [7410](https://github.com/MonetDB/MonetDB/issues/7410): SIGSEGV cause database corruption