QuasarDB "Apollodorus" 3.7.0 available

We are very pleased to announce the immediate availability of QuasarDB 3.7.0.


This release focuses on performance improvement and lower memory usage.


New features


  • [query] Support for timestamp comparisons in WHERE clauses
  • [query] New function to count adjacent differences in a column
  • [query] Allow to insert NULL strings in INSERT INTO statements
  • [query] Allow WHERE (t.)col1 = (t.)col2 with multiple tables (e.g. with a find statement)


Fixes and improvements


  • [daemon] Blob on-disk and in-memory speed and size optimizations (up to X4 more memory efficient, X2 faster insertions)
  • [daemon] Improve eviction and overall memory usage
  • [daemon] Removed a bottleneck on concurrent read-only operations on the same table


Try it now!


QuasarDB "Antipater" 3.6.0 Released

We are very pleased to announce the immediate availability of QuasarDB 3.6.0.


This release brings three important enhancement to the analytical capabilities of QuasarDB.


First, column to column comparison is now supported. Second, we've greatly increased the capabilities of the ASOF feature. You can learn more about ASOF in this blog post.


Last but not least, function composition in the SELECT clause is now supported.


New features


  • Support for ASOF against a generated time range
  • Increase the flexibility of WHERE to allow for column to column comparisons
  • Allow for function composition in the SELECT clause
  • License expiration time is now available in the statistics


Fixes and improvements


  • Properly handle NULL values in GROUP BY
  • Protocol version mismatch are no longer considered as “internal errors”
  • Ensure that network and timeout errors are always returned as network errors and not “internal errors”
  • An aggressive optimization could make the shell display non-existing null values
  • Blobs could be stored in the wrong column family resulting in unexpected “alias not found” errors
  • Greatly improve eviction heuristics in the case of bulk insertion
  • Fix signal handling to prevent deadlocks on SIGABRT or SIGSEGV


Try it now!


New release process

We are pleased to inform our customers that we are changing our release process.


Starting from February 3rd, 2020, we will release a new version of QuasarDB every first Monday of the month.


Every third Monday of the month, a release candidate will be made available.


You can learn more about the rationale behind this change in this blog post.