Changeset: 7dd325ed4919 for MonetDB URL: https://dev.monetdb.org/hg/MonetDB/rev/7dd325ed4919 Modified Files: ChangeLog.Jul2021 clients/ChangeLog.Jul2021 gdk/ChangeLog.Jul2021 sql/ChangeLog.Jul2021 Branch: Jul2021 Log Message:
Changelog blurbs. diffs (92 lines): diff --git a/ChangeLog.Jul2021 b/ChangeLog.Jul2021 --- a/ChangeLog.Jul2021 +++ b/ChangeLog.Jul2021 @@ -1,6 +1,3 @@ # ChangeLog file for devel # This file is updated with Maddlog -* Thu Apr 15 2021 svetlin <[email protected]> -- preserve in query comments - diff --git a/clients/ChangeLog.Jul2021 b/clients/ChangeLog.Jul2021 --- a/clients/ChangeLog.Jul2021 +++ b/clients/ChangeLog.Jul2021 @@ -1,3 +1,8 @@ # ChangeLog file for clients # This file is updated with Maddlog +* Tue Jul 20 2021 Sjoerd Mullender <[email protected]> +- The MonetDB stethoscope has been removed. There is now a separate + package available with PIP (monetdb_stethoscope) or as an RPM or DEB + package (stethoscope) from the monetdb.org repository. + diff --git a/gdk/ChangeLog.Jul2021 b/gdk/ChangeLog.Jul2021 --- a/gdk/ChangeLog.Jul2021 +++ b/gdk/ChangeLog.Jul2021 @@ -1,6 +1,18 @@ # ChangeLog file for GDK # This file is updated with Maddlog +* Tue Jul 20 2021 Sjoerd Mullender <[email protected]> +- A new type, called msk, was introduced. This is a bit mask type. + In a bat with type msk, each row occupies a single bit, so 8 rows are + stored in a single byte. There is no NULL value for this type. +- The function of the BAT iterator (type BATiter, function bat_iterator) + has been expanded. The iterator now contains more information about + the BAT, and it contains a pointer to the heaps (theap and tvheap) + that are stable, at least in the sense that they will remain available + even when parallel threads update the BAT and cause those heaps to grow + (and therefore possibly move in memory). A call to bat_iterator must + now be accompanied by a call to bat_iterator_end. + * Mon Mar 29 2021 Sjoerd Mullender <[email protected]> - Implemented function BUNreplacemultiincr to replace multiple values in a BAT in one go, starting at a given position. diff --git a/sql/ChangeLog.Jul2021 b/sql/ChangeLog.Jul2021 --- a/sql/ChangeLog.Jul2021 +++ b/sql/ChangeLog.Jul2021 @@ -1,6 +1,26 @@ # ChangeLog file for sql # This file is updated with Maddlog +* Tue Jul 20 2021 Niels Nes <[email protected]> +- In the Jul2021 release the storage and transaction layers have + undergone major changes. The goal of these changes is robust + performance under inserts/updates and deletes and lowering the + transaction startup costs, allowing faster (small) queries. Where + the old transaction layer duplicated a lot of data structures during + startup, the new layer shares the same tree. Using object + timestamps the isolation of object is guaranteed. On the storage + side the timestamps indicate whether a row is visible (deleted or + valid), to a transaction as well. The changes also give some slight + changes on the perceived transactional behavior. The new + implementation uses shared structures among all transactions, which + do not allow multiple changes of the same object. And we then + follow the principle of the first writer wins, i.e., if a + transaction creates a table with name 'table_name', and concurrently + one other transaction does the same the later of the two will fail + with a concurrency conflict error message (even if the first writer + never commits). We expect most users not to notice this change, as + such schema changes aren't usually done concurrently. + * Tue May 11 2021 Sjoerd Mullender <[email protected]> - There is now a function sys.current_sessionid() to return the session ID of the current session. This ID corresponds with the sessionid in @@ -11,13 +31,16 @@ conditions, so a renovation was made. As a consequence, subqueries now have to be disabled on merge join conditions. +* Thu Apr 15 2021 svetlin <[email protected]> +- preserve in-query comments + * Tue Mar 16 2021 Pedro Ferreira <[email protected]> - Use of CTEs inside UPDATE and DELETE statements are now more restrict. Previously they could be used without any extra specification in the query (eg. with "v1"("c1") as (...) delete from "t" where "t"."c1" = "v1"."c1"), however this was not conformant with the SQL standard. In order to use them, they must be specified in the FROM - clause in UPDATE statments or inside a subquery. + clause in UPDATE statements or inside a subquery. * Mon Nov 30 2020 Pedro Ferreira <[email protected]> - Added 'schema path' property to user, specifying a list of schemas _______________________________________________ checkin-list mailing list [email protected] https://www.monetdb.org/mailman/listinfo/checkin-list
