Changeset: 700e099bfee8 for MonetDB
URL: https://dev.monetdb.org/hg/MonetDB/rev/700e099bfee8
Modified Files:
        MonetDB.spec
        debian/changelog
        gdk/ChangeLog-Archive
        gdk/ChangeLog.Jul2021
        misc/packages/deb/changelog
        misc/packages/rpm/changelog
        monetdb5/ChangeLog-Archive
        monetdb5/ChangeLog.Jul2021
        sql/ChangeLog-Archive
        sql/ChangeLog.Jul2021
        tools/merovingian/ChangeLog-Archive
        tools/merovingian/ChangeLog.Jul2021
Branch: Jul2021
Log Message:

Moved contents of ChangeLog.Jul2021 to MonetDB.spec, debian/changelog and 
ChangeLog-Archive.


diffs (truncated from 582 to 300 lines):

diff --git a/MonetDB.spec b/MonetDB.spec
--- a/MonetDB.spec
+++ b/MonetDB.spec
@@ -84,7 +84,7 @@ Group: Applications/Databases
 License: MPLv2.0
 URL: https://www.monetdb.org/
 BugURL: https://bugs.monetdb.org/
-Source: 
https://www.monetdb.org/downloads/sources/Jul2021-SP8/%{name}-%{version}.tar.bz2
+Source: 
https://www.monetdb.org/downloads/sources/Jul2021-SP9/%{name}-%{version}.tar.bz2
 
 # The Fedora packaging document says we need systemd-rpm-macros for
 # the _unitdir and _tmpfilesdir macros to exist; however on RHEL 7
@@ -846,6 +846,73 @@ else
 fi
 
 %changelog
+* Thu Feb 23 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- Rebuilt.
+
+* Mon Feb 20 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- gdk: A race condition was fixed where certain write-ahead log messages
+  could get intermingled, resulting in a corrupted WAL file.
+- gdk: 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.
+
+* Mon Feb 13 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- gdk: 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.
+- gdk: 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).
+
+* Mon Feb 13 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- sql: An insert into a table from which a column was dropped in a parallel
+  transaction was incorrectly not flagged as a transaction conflict.
+
+* Mon Jan 16 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- gdk: Fixed a race condition that could lead to a bat being added to the SQL
+  catalog but nog being made persistent, causing a subsequent restart
+  of the system to fail (and crash).
+
+* Fri Dec 16 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- sql: Added some error checking to prevent crashes.  Errors would mainly
+  occur under memory pressure.
+
+* Wed Dec 14 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- gdk: Fixed a race condition where a hash could have been created on a
+  bat using the old bat count while in another thread the bat count
+  got updated.  This would make the hash be based on too small a size,
+  causing failures later on.
+
+* Wed Dec 14 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- sql: Fixed cleanup after a failed allocation where the data being cleaned
+  up was unitialized but still used as pointers to memory that also had
+  to be freed.
+
+* Thu Dec  8 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- gdk: When extending a bat failed, the capacity had been updated already and
+  was therefore too large.  This could then later cause a crash.  This has
+  been fixed by only updating the capacity if the extend succeeded.
+
+* Wed Dec  7 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- gdk: A bug was fixed when dealing with copy-on-write memory maps.  These can
+  occur for some bats used by the write-ahead log code when they grow
+  large enough.
+
+* Wed Dec  7 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- sql: A bug was fixed when optimizing combining of range select
+  subexpressions.
+- sql: If there was an error in one of the special commands to the server
+  (e.g. setting the reply size for result sets), the server could get
+  into an infinite loop.  This has been fixed.
+- sql: Fixed a double cleanup after a failed allocation in COPY INTO.  The
+  double cleanup could cause a crash due to a race condition it enabled.
+
+* Wed Oct 19 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- monetdb5: Fix a bug where the MAL optimizer would use the starttime of the
+  previous query to determine whether a query timeout occurred.
+
+* Wed Oct 12 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- merovingian: Stop logging references to monetdbd's logfile in said logfile.
+
 * Fri Aug 26 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.27-20220826
 - Rebuilt.
 
diff --git a/debian/changelog b/debian/changelog
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,109 @@
+monetdb (11.41.29) unstable; urgency=low
+
+  * Rebuilt.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Thu, 23 Feb 2023 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * gdk: A race condition was fixed where certain write-ahead log messages
+    could get intermingled, resulting in a corrupted WAL file.
+  * gdk: 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.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Mon, 20 Feb 2023 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * gdk: 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.
+  * gdk: 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).
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Mon, 13 Feb 2023 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * sql: An insert into a table from which a column was dropped in a parallel
+    transaction was incorrectly not flagged as a transaction conflict.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Mon, 13 Feb 2023 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * gdk: Fixed a race condition that could lead to a bat being added to the SQL
+    catalog but nog being made persistent, causing a subsequent restart
+    of the system to fail (and crash).
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Mon, 16 Jan 2023 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * sql: Added some error checking to prevent crashes.  Errors would mainly
+    occur under memory pressure.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Fri, 16 Dec 2022 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * gdk: Fixed a race condition where a hash could have been created on a
+    bat using the old bat count while in another thread the bat count
+    got updated.  This would make the hash be based on too small a size,
+    causing failures later on.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Wed, 14 Dec 2022 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * sql: Fixed cleanup after a failed allocation where the data being cleaned
+    up was unitialized but still used as pointers to memory that also had
+    to be freed.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Wed, 14 Dec 2022 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * gdk: When extending a bat failed, the capacity had been updated already and
+    was therefore too large.  This could then later cause a crash.  This has
+    been fixed by only updating the capacity if the extend succeeded.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Thu, 8 Dec 2022 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * gdk: A bug was fixed when dealing with copy-on-write memory maps.  These 
can
+    occur for some bats used by the write-ahead log code when they grow
+    large enough.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Wed, 7 Dec 2022 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * sql: A bug was fixed when optimizing combining of range select
+    subexpressions.
+  * sql: If there was an error in one of the special commands to the server
+    (e.g. setting the reply size for result sets), the server could get
+    into an infinite loop.  This has been fixed.
+  * sql: Fixed a double cleanup after a failed allocation in COPY INTO.  The
+    double cleanup could cause a crash due to a race condition it enabled.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Wed, 7 Dec 2022 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * monetdb5: Fix a bug where the MAL optimizer would use the starttime of the
+    previous query to determine whether a query timeout occurred.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Wed, 19 Oct 2022 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * merovingian: Stop logging references to monetdbd's logfile in said logfile.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Wed, 12 Oct 2022 10:49:38 +0100
+
 monetdb (11.41.27) unstable; urgency=low
 
   * Rebuilt.
diff --git a/gdk/ChangeLog-Archive b/gdk/ChangeLog-Archive
--- a/gdk/ChangeLog-Archive
+++ b/gdk/ChangeLog-Archive
@@ -1,6 +1,41 @@
 # DO NOT EDIT THIS FILE -- MAINTAINED AUTOMATICALLY
 # This file contains past ChangeLog entries
 
+* Mon Feb 20 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- 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.
+
+* Mon Feb 13 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- 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).
+
+* Mon Jan 16 2023 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- Fixed a race condition that could lead to a bat being added to the SQL
+  catalog but nog being made persistent, causing a subsequent restart
+  of the system to fail (and crash).
+
+* Wed Dec 14 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- Fixed a race condition where a hash could have been created on a
+  bat using the old bat count while in another thread the bat count
+  got updated.  This would make the hash be based on too small a size,
+  causing failures later on.
+
+* Thu Dec  8 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- When extending a bat failed, the capacity had been updated already and
+  was therefore too large.  This could then later cause a crash.  This has
+  been fixed by only updating the capacity if the extend succeeded.
+
+* Wed Dec  7 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.29-20230223
+- A bug was fixed when dealing with copy-on-write memory maps.  These can
+  occur for some bats used by the write-ahead log code when they grow
+  large enough.
+
 * Wed Aug 10 2022 Sjoerd Mullender <sjo...@acm.org> - 11.41.27-20220826
 - A bug was fixed when upgrading a database from the Oct2020 releases
   (11.39.X) or older when the write-ahead log (WAL) was not empty and
diff --git a/gdk/ChangeLog.Jul2021 b/gdk/ChangeLog.Jul2021
--- a/gdk/ChangeLog.Jul2021
+++ b/gdk/ChangeLog.Jul2021
@@ -1,38 +1,3 @@
 # ChangeLog file for GDK
 # This file is updated with Maddlog
 
-* Mon Feb 20 2023 Sjoerd Mullender <sjo...@acm.org>
-- 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.
-
-* Mon Feb 13 2023 Sjoerd Mullender <sjo...@acm.org>
-- 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).
-
-* Mon Jan 16 2023 Sjoerd Mullender <sjo...@acm.org>
-- Fixed a race condition that could lead to a bat being added to the SQL
-  catalog but nog being made persistent, causing a subsequent restart
-  of the system to fail (and crash).
-
-* Wed Dec 14 2022 Sjoerd Mullender <sjo...@acm.org>
-- Fixed a race condition where a hash could have been created on a
-  bat using the old bat count while in another thread the bat count
-  got updated.  This would make the hash be based on too small a size,
-  causing failures later on.
-
-* Thu Dec  8 2022 Sjoerd Mullender <sjo...@acm.org>
-- When extending a bat failed, the capacity had been updated already and
-  was therefore too large.  This could then later cause a crash.  This has
-  been fixed by only updating the capacity if the extend succeeded.
-
-* Wed Dec  7 2022 Sjoerd Mullender <sjo...@acm.org>
-- A bug was fixed when dealing with copy-on-write memory maps.  These can
-  occur for some bats used by the write-ahead log code when they grow
-  large enough.
-
diff --git a/misc/packages/deb/changelog b/misc/packages/deb/changelog
--- a/misc/packages/deb/changelog
+++ b/misc/packages/deb/changelog
@@ -1,3 +1,109 @@
+monetdb (11.41.29) unstable; urgency=low
+
+  * Rebuilt.
+
+ -- Sjoerd Mullender <sjo...@acm.org>  Thu, 23 Feb 2023 10:49:38 +0100
+
+monetdb (11.41.29) unstable; urgency=low
+
+  * gdk: A race condition was fixed where certain write-ahead log messages
+    could get intermingled, resulting in a corrupted WAL file.
_______________________________________________
checkin-list mailing list -- checkin-list@monetdb.org
To unsubscribe send an email to checkin-list-le...@monetdb.org

Reply via email to