• Increase the auth store database size to 2 GiB so that we can index more keys by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6134

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.34.2...v1.34.3

QuestDB 9.3.2 continues the trend of performance upgrades and bugfixes, with some additional new features. Importantly, we introduce the new TICK syntax, a compact DSL for expressing time intervals, alongside faster aggregations, improved applicability of interval scans, and fast parquet queries.

For any questions or feedback, please join us on Slack or on Discourse.

See also our prettier release notes page.

The Temporal Interval Calendar Kit (TICK is a new DSL for expressing complex time ranges and intervals in a compact, easy-to-use format.

For example, let's say that you want to query one month of data from NYSE, only including trading days and hours. The data in the database is stored in UTC format, so you'd need to convert to different time zones, and build a very complex WHERE clause with ANDs and ORs. Or, alternatively, send lots of narrow queries and combine the results.

Instead, you can express this in a simple string:

-- NYSE trading hours on workdays for January
SELECT * FROM trades
WHERE ts IN '2024-01-[01..31]T09:30@America/New_York#workday;6h29m';

Reading this from left to right, we will the days in 2024-01 in the range of 01..31 (all of them), with the interval beginning at 09:30 in New York time, only considering working days, and the interval ending after 6h29m on each day (inclusive, so at 16:00 New York time).

We then compile this to an efficient interval scan, with the time filtering pushed down:

 intervals: [
    ("2024-01-01T14:30:00.000000Z","2024-01-01T20:59:59.999999Z"),     

    ("2024-01-02T14:30:00.000000Z","2024-01-02T20:59:59.999999Z"),

    ("2024-01-03T14:30:00.000000Z","2024-01-03T20:59:59.999999Z"),

    ...
]

This syntax makes it easier to construct complex intervals, and keep confidence that the execution plan will be optimal.

Please see the TICK docs for more information.

Let's say you are monitoring trading data, and you track what the max trading price was over an hourly period. You can express that like this:

SELECT timestamp, symbol, max(price)
FROM trades
WHERE timestamp IN today()
AND symbol IN ('BTC-USDT', 'ETH-USDT')
SAMPLE BY 1h;

But now we have a problem - at what time or trade was that the max price?

Using arg_max, we can extract values from the row where the price was max:

SELECT timestamp, symbol, max(price), arg_max(timestamp, price)
FROM trades
WHERE timestamp IN today()
AND symbol IN ('BTC-USDT', 'ETH-USDT')
SAMPLE BY 1h;

Pretty handy!

geomean(D) calculates the geometric mean for a set of positive numbers; this is a useful average variant, which improves accuracy for data with large outliers, and commonly used for growth rate calculations.

For more details, please check out the aggregate function documentation.

We've introduced new exponential moving average (EMA) window functions. This smooths out your data base on a smoothing and time period.

Additionally, we've added a volume-weighted variant (VWEMA), which is commonly used for trading data, allowing for smoothing of the function whilst still prioritising higher-volume trades.

Here's an example of the syntax:

-- Standard average
avg(value) OVER (window_definition)

-- Exponential Moving Average (EMA)
avg(value, kind, param) OVER (window_definition)

-- Volume-Weighted Exponential Moving Average (VWEMA)
avg(value, kind, param, volume) OVER (window_definition)

percent_rank returns the relative rank of a row within a group of values. This is calculated based on the number of rows within the group, and its position.

For more information, please see the window functions documentation.

• QuestDB will now optimise time-range queries over tables where the range uses a constant dateadd offset.
  • e.g. WHERE dateadd('m', 15, timestamp) = '2022-03-08T18:30:00Z'
• QuestDB will optimise time filters that include OR clauses:
  • e.g. WHERE timestamp IN '2018-01-01' OR timestamp IN '2018-01-02' OR timestamp IN '2018-01-03'
• We've improved how time-range pushdown is handled within nested queries:
  • e.g. SELECT * FROM (SELECT dateadd('h', -1, timestamp) as ts, price FROM trades) WHERE ts in '2022'

• We have significantly sped-up querying parquet queries by optimising how row-groups are decoded, giving up to a 6x performance boost versus the last release.
• We've optimised how file mappings are handled, removing sporadic query latency increases over extremely concurrent query workloads.

• feat(sql): volume-weighted exponential moving average (VWEMA) window function by @bluestreak01 in https://github.com/questdb/questdb/pull/6651
• feat(sql): add arg_min() and arg_max() aggregate functions by @bluestreak01 in https://github.com/questdb/questdb/pull/6652
• feat(sql): implement EMA window function via avg() by @bluestreak01 in https://github.com/questdb/questdb/pull/6650
• fix(ilp): prevent writes going to the wrong place after a table rename by @nwoolmer in https://github.com/questdb/questdb/pull/6654
• feat(sql): add bool_and() and bool_or() aggregate functions by @bluestreak01 in https://github.com/questdb/questdb/pull/6658
• feat(sql): add bit_and(), bit_or(), and bit_xor() aggregate functions by @bluestreak01 in https://github.com/questdb/questdb/pull/6660
• feat(sql): add geomean() aggregate function by @bluestreak01 in https://github.com/questdb/questdb/pull/6656
• fix(sql): prevent SIGSEGV in window join by awaiting workers before freeing cache by @bluestreak01 in https://github.com/questdb/questdb/pull/6662
• feat(sql): recognize dateadd predicates in time intrinsic filters by @puzpuzpuz in https://github.com/questdb/questdb/pull/6666
• fix(sql): potential segfault on vectorized GROUP BY query timeout by @puzpuzpuz in https://github.com/questdb/questdb/pull/6667
• feat(sql): support nested window functions with deduplication optimization by @bluestreak01 in https://github.com/questdb/questdb/pull/6643
• feat(sql): add within_box, within_radius, and geo_within_radius_latlon functions by @bluestreak01 in https://github.com/questdb/questdb/pull/6664
• feat(sql): recognize OR of timestamp IN predicates as interval intrinsics by @bluestreak01 in https://github.com/questdb/questdb/pull/6673
• fix(sql): handle unbalanced quotes in SQL line comments by @bluestreak01 in https://github.com/questdb/questdb/pull/6684
• perf(core): avoid contention across concurrent queries on expensive file operation by @mtopolnik in https://github.com/questdb/questdb/pull/6688
• perf(sql): apply scan optimization for first/last/min/max(timestamp) as function argument by @kafka1991 in https://github.com/questdb/questdb/pull/6690
• fix(sql): error on group by with many aggregate functions by @puzpuzpuz in https://github.com/questdb/questdb/pull/6689
• feat(sql): add length_bytes() function for varchars by @puzpuzpuz in https://github.com/questdb/questdb/pull/6685
• fix(sql): fix reverse-order argument parsing in multi-arg window function by @mtopolnik in https://github.com/questdb/questdb/pull/6697
• fix(sql): proper error message when timestamp used along another join key in ASOF/LT join by @mtopolnik in https://github.com/questdb/questdb/pull/6698
• fix(sql): fix an issue where the DECLAREd symbols weren't honored when parsing function arguments by @mtopolnik in https://github.com/questdb/questdb/pull/6700
• fix(sql): fix parquet read failure on chained window join by @kafka1991 in https://github.com/questdb/questdb/pull/6676
• fix(sql): resolve 'Invalid column' error in WINDOW JOIN with aliased columns by @bluestreak01 in https://github.com/questdb/questdb/pull/6701
• feat(sql): TICK - Temporal Interval Calendar Kit for interval literals by @bluestreak01 in https://github.com/questdb/questdb/pull/6674
• fix(pgwire): prepared batch with same SQL returns corrupted results by @kafka1991 in https://github.com/questdb/questdb/pull/6706
• fix(sql): fix nanosecond timestamp handling in tables() and wal_transactions() by @mtopolnik in https://github.com/questdb/questdb/pull/6704
• feat(sql): timestamp predicate pushdown through virtual models with dateadd offset by @bluestreak01 in https://github.com/questdb/questdb/pull/6702
• feat(sql): implement percent_rank() window function by @bluestreak01 in https://github.com/questdb/questdb/pull/6712
• fix(sql): fix order by position resolution with window functions over CTEs by @bluestreak01 in https://github.com/questdb/questdb/pull/6716
• feat(sql): extend TICK date variable arithmetic with additional time units by @bluestreak01 in https://github.com/questdb/questdb/pull/6711
• perf(sql): optimize parquet decode rowgroup performance by @kafka1991 in https://github.com/questdb/questdb/pull/6632
• fix(core): broken logging in TableWriter that may lead to unresponsive instance by @puzpuzpuz in https://github.com/questdb/questdb/pull/6720
• fix(core): fix dictionary and bitpack encoding for symbol columns in parquet by @kafka1991 in https://github.com/questdb/questdb/pull/6708
• feat(ui): ai assistant improvements by @emrberk in https://github.com/questdb/ui/pull/529

• @mghildiy made their first contribution in https://github.com/questdb/questdb/pull/6644

Full Changelog: https://github.com/questdb/questdb/compare/9.3.1...9.3.2

• add getter for decoded path by @ilanachalom in https://github.com/Netflix/zuul/pull/2056
• bump release version by @ilanachalom in https://github.com/Netflix/zuul/pull/2059
• Add backward compatible constructors by @lalernehl in https://github.com/Netflix/zuul/pull/2060
• Bump release version by @lalernehl in https://github.com/Netflix/zuul/pull/2061

• @ilanachalom made their first contribution in https://github.com/Netflix/zuul/pull/2056

Full Changelog: https://github.com/Netflix/zuul/compare/v3.3.2...v3.3.3

Download page What's new highlights

• API: Add missing scope check on dashboards #116888, @Proximyst
• Avatar: Require sign-in, remove queue, respect timeout #116893, @macabu
• ElasticSearch: Update annotation time-range properties #115566, @aangelisc
• Explore: Reset legend when a new query is run #116590, @ifrost
• Go: Update to 1.25.6 #116396, @macabu

• Alerting: Fix a race condition panic in ResetStateByRuleUID #115680, @alexander-akhmetov
• Alerting: Fix data source recording rules editor #116303, @soniaAguilarPeiron

Download page What's new highlights

• API: Add missing scope check on dashboards #116889, @Proximyst
• Avatar: Require sign-in, remove queue, respect timeout #116895, @macabu
• Docs: Clarify section title for repeating rows and tabs #115345, @imatwawana
• ElasticSearch: Update annotation time-range properties #115565, @aangelisc
• Explore: Reset legend when a new query is run #116589, @ifrost
• Go: Update to 1.25.6 #116399, @macabu

• Alerting: Fix a race condition panic in ResetStateByRuleUID #115694, @alexander-akhmetov

Download page What's new highlights

• API: Add missing scope check on dashboards #116890, @Proximyst
• Avatar: Require sign-in, remove queue, respect timeout #116896, @macabu
• Go: Update to 1.25.6 #116400, @macabu

• Alerting: Fix a race condition panic in ResetStateByRuleUID #115693, @alexander-akhmetov

Download page What's new highlights

• API: Add missing scope check on dashboards #116892, @Proximyst
• Avatar: Require sign-in, remove queue, respect timeout #116897, @macabu
• Go: Update to 1.25.6 #116401, @macabu

• Alerting: Fix a race condition panic in ResetStateByRuleUID #115692, @alexander-akhmetov

This patch fixes an accidental breaking change in v1.34.1 where Meilisearch would not start with a configuration file if experimental_allowed_ip_networks was not defined.

• Meilisearch Cloud users do not need to update as they were not affected by this regression
• We recommend that OSS users upgrade to v1.34.2

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.34.1...v1.34.2

OpenSSL 3.0.19 is a security patch release. The most severe CVE fixed in this release is High.

This release incorporates the following bug fixes and mitigations:

• Fixed Stack buffer overflow in CMS AuthEnvelopedData parsing. (CVE-2025-15467)

• Fixed Heap out-of-bounds write in BIO_f_linebuffer on short writes. (CVE-2025-68160)

• Fixed Unauthenticated/unencrypted trailing bytes with low-level OCB function calls. (CVE-2025-69418)

• Fixed Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion. (CVE-2025-69419)

• Fixed Missing ASN1_TYPE validation in TS_RESP_verify_response() function. (CVE-2025-69420)

• Fixed NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex() function. (CVE-2025-69421)

• Fixed Missing ASN1_TYPE validation in PKCS#12 parsing. (CVE-2026-22795)

• Fixed ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function. (CVE-2026-22796)