Update dependency org.questdb:questdb to v9.1.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
org.questdb:questdb (source)	9.0.3 -> 9.1.0

---

Release Notes

questdb/questdb (org.questdb:questdb)

v9.1.0

Compare Source

QuestDB 9.1.0 is now available. It is a feature-rich release bringing nanosecond timestamp data type, performance and stability improvements.

Highlights

• Nanosecond timestamps: New TIMESTAMP_NS type adds nanosecond precision to time-series data (#​5685).
• Continuous profiling: Integrated async-profiler lets you capture CPU and memory flame graphs continuously or on demand (#​6150).
• JOIN improvements: Support for all JOIN types including RIGHT OUTER and FULL OUTER, plus dramatically faster ASOF JOINs on indexed columns (#​6158, #​6076).
• New SQL functions: Added timestamp and long window functions, plus visibility into symbol table size via SHOW COLUMNS (#​6130, #​6128).
• Performance wins:
  • Symbol map auto-scaling: Eliminates ingestion bottlenecks from fixed symbol capacity. Now millions of distinct values ingest in seconds instead of hours.
  • Faster IN (...) queries on large lists (breaking change 💥).

Nanosecond timestamp support 🛡️

QuestDB now supports nanosecond precision with a new data type: TIMESTAMP_NS.

• The existing TIMESTAMP type remains microsecond precision and is unchanged.
• TIMESTAMP_NS can be used in all contexts where TIMESTAMP is valid (columns, functions, joins, ordering, etc.).
• Migration: No changes are required for existing tables. They will continue to use TIMESTAMP (microsecond).
• Rollback compatibility:
  • If you do not create tables with TIMESTAMP_NS, you can safely roll back to QuestDB 9.0.3 or earlier.
  • If you do create tables with TIMESTAMP_NS, older versions will not recognize this type. Such tables must be dropped before rolling back.
• Drivers and client libraries: TIMESTAMP_NS is supported by existing QuestDB drivers (JDBC, Go, Python, etc.), provided you are on a recent release of the driver. No protocol upgrade or client code changes are required.

Symbol map auto-scaling (opt-in)

Symbol column map capacity now scales automatically with the number of distinct values, removing one of the biggest friction points in high-ingestion workloads.

• Before: symbol map capacity was fixed at table creation.

  • If undersized, ingestion performance could degrade by up to 1000×, often making ingestion practically impossible.
  • For example, on default settings the system would bog down at ~1,000,000 unique symbols, taking several hours to ingest that data (unless the user had pre-sized the symbol map correctly).

• Now: with auto-scaling enabled, symbol capacity grows dynamically:

  • ~2,000,000 distinct values ingested in 2.5 seconds (vs hours).
  • ~40,000,000 distinct values ingested in 2.5 minutes (vs never finishing before).

• Backward compatibility:

  • Auto-scaling is opt-in to preserve compatibility.
  • Enabling it stores metadata in a new structure that older versions cannot read.
  • If rollback is required, data does not need to be dropped, but some manual file renaming steps are necessary. Users can contact QuestDB support for guidance.

• Opt-in instructions:

Enable via configuration property, system's restart is not required:

cairo.auto.scale.symbol.capacity=true

Continuous profiling support (opt-in)

QuestDB now ships with the Async Profiler integrated out-of-the-box. This dramatically reduces friction when diagnosing performance issues such as high CPU usage or queries that appear slow.

• Ease of use: the profiler is bundled, no manual installation required.
• Opt-in: profiling has no impact on performance unless enabled.
• Performance impact:
  • 0% overhead when not in use.
  • ~10% overhead when the profiler is actively connected.
• Modes of use:
  1. Start with profiling enabled – less common, but can help during development or long-running load tests.
  2. Attach to a running instance – the most useful mode, allows “catching the system in the act” when issues are intermittent or difficult to reproduce.

Examples

Start a 30s CPU profiling session and generate an interactive HTML flamegraph:

questdb.sh profile -- -e cpu -d 30 -f /tmp/cpu.html

SQL & Query Engine

• Nanosecond timestamp support for ultra-high resolution time-series workloads (#​5685).
• New window functions for timestamp and long data types (#​6130).
• Symbol table size visibility added to SHOW COLUMNS (#​6128).
• Optimized IN (...) comparisons on long lists — breaking change 💥 (#​6109).
• Enhanced JOIN execution with multiple improvements (#​6076).
• Faster ASOF JOIN on indexed symbol columns (#​6158).
• Vectorized avg(short) and improved sum() functions memory usage (#​6166).
• GROUP BY queries now rewrite trivial expressions over the same column for better performance (#​6043).
• Improved null-handling in INSERT INTO SELECT queries with implicit casting (#​5586).
• Consistent behavior of EXPLAIN command (#​6200).
• Fixed NPE in DISTINCT queries with dependent columns (#​6080).
• Fixed compilation error for symbol column to symbol cast in GROUP BY queries (#​6072).
• Fixed nanosecond precision issues in ASOF JOIN TOLERANCE and CSV imports (#​6183).
• Prevented multiple DECLARE statements in single query block (#​6161).
• Fixed rare assertion error after metadata changes (#​6195).

Ingestion (ILP)

• Improved handling of symbol ingestion with double column conversion (#​6143).
• Retry logic fixed when fetching server protocol version (#​6099).
• Support for configuring multiple possible database endpoints (#​6074).
• Improved connection handling — now avoids closing connections on protocol errors (#​6190).

Core & Operations

Continuous profiling support

QuestDB now integrates the Async Profiler for low-overhead performance diagnostics.

• Modes:
  • Continuous profiling at startup (questdb.sh start -p)
  • On-demand attach to running instances for CPU or allocation traces
• Outputs:
  • Interactive HTML flame graphs
  • JFR (Java Flight Recorder) output (#​6150)

Threading and resource usage

• Materialized view refreshes now run on a dedicated thread pool (#​6111)

Reliability fixes

• Fixed rare index reader memory error on partition drop (#​6087)
• Fixed suspended table showing wrong writerTxn (#​6090)
• Fixed table read timeout after non-WAL drop/re-create (#​6095)
• Fixed rare suspension on index drop (#​6147)
• Fixed misleading “table locked” error appearing before write failures (#​6152)
• Fixed failure handling on column renames (#​5752)
• Fixed spurious “cannot mmap” errors (#​6104)
• Fixed incorrect error handling that could leave table reader in an inconsistent state (#​6108)
• Fixed memory tags used in Path (#​6124)
• Fixed assertion exception in writer triggered by OS errors (#​6204)

Breaking change 💥

IN list queries now use hash-based lookups instead of binary search, delivering significant performance gains for large lists.

• Performance: Faster execution for queries with thousands of IN values.
• Configuration: JIT compilation is skipped for lists larger than cairo.sql.jit.max.in.list.size.threshold (default: 10,000).
• Behaviour: Results remain equivalent, but execution order and memory usage may differ in edge cases.

Migration guidance:

• No SQL syntax changes are required
• If you notice regressions for small lists or need JIT for large lists, adjust cairo.sql.jit.max.in.list.size.threshold.
• Benchmark your workloads to tune the threshold for optimal results.
• Expect faster performance for large IN lists out of the box.

This change matters most for queries with very large IN lists (thousands of values), often seen in data filtering, batch imports, or security/ACL checks. These workloads will now execute much faster by default.

What's Changed

• build: 9.0.3 by @​jerrinot in #​6086
• fix(core): fix rare index reader memory on partition drop by @​jerrinot in #​6087
• fix(core): fix suspended tables showing wrong writerTxn in wal_tables by @​ideoma in #​6090
• fix(core): fix table reading timeout error after non-wal table dropped and re-created by @​ideoma in #​6095
• fix(ilp): fix retrying when fetching server protocol version by @​jerrinot in #​6099
• fix(sql): fix NPE when distinct query contains columns with dependencies. by @​kafka1991 in #​6080
• fix(core): fix spurious "cannot mmap" errors by @​bluestreak01 in #​6104
• fix(core): fix incorrect error handling, which can leave table reader in an inconsistent state by @​bluestreak01 in #​6108
• perf(core): run mat view refresh on a separate thread pool by @​ideoma in #​6111
• fix(core): fix memory tags used in Path by @​ideoma in #​6124
• perf(sql): breaking change 💥- speed up IN comparisons on long lists by @​nwoolmer in #​6109
• fix(log) : remove external US IP from default alertTargets(#​6134) by @​skytech9999 in #​6135
• feat(sql): add timestamp and long window functions by @​bluestreak01 in #​6130
• feat(sql): add symbol table size to SHOW COLUMNS SQL by @​puzpuzpuz in #​6128
• feat(core): nanosecond timestamp by @​bluestreak01 in #​5685
• fix(ilp): fix incorrectly symbol value when use doublecolumn ingest to symbol column by @​kafka1991 in #​6143
• fix(core): fix misleading table locked error appearing before write failure by @​ideoma in #​6152
• feat(core): add continuous profiling support with async-profiler by @​jerrinot in #​6150
• fix(sql): compilation error for symbol column to symbol cast in group by query by @​puzpuzpuz in #​6072
• fix(core): fix failure handling on column renames by @​ideoma in #​5752
• fix(core): fix rare error on index drop that can suspend table by @​ideoma in #​6147
• fix(sql): prevent multiple DECLARE statements in single query block by @​kafka1991 in #​6161
• fix(sql): fix nanosecond issues in ASOF join TOLERANCE and CSV imports by @​kafka1991 in #​6183
• perf(sql): vectorize avg(short) and improve sum() functions memory usage by @​puzpuzpuz in #​6166
• feat(sql): speed up ASOF JOIN on indexed symbol column by @​mtopolnik in #​6158
• fix(sql): improve null-handling of INSERT INTO SELECT queries that rely on implicit casting by @​nwoolmer in #​5586
• fix(ilp): avoid closing connection on protocol errors by @​puzpuzpuz in #​6190
• perf(sql): rewrite trivial expressions over same column in GROUP BY queries by @​puzpuzpuz in #​6043
• fix(core): rare assertion error in SQL after metadata change by @​bluestreak01 in #​6195
• fix(sql): consistent behaviour of EXPLAIN command by @​glasstiger in #​6200
• fix(core): fix assertion exception in writer, which is triggered by OS error by @​bluestreak01 in #​6204
• feat(sql): join enhancements by @​kafka1991 in #​6076
• feat(ilp): add support for configuring multiple possible database endpoints by @​nwoolmer in #​6074
• fix(pgwire): improve support for bind variables as function arguments by @​bluestreak01 in #​5999
• fix(core): fd leak in index writer initialization by @​puzpuzpuz in #​6211
• feat(sql): implement mode(Ø/T/L/K/S/D) group by functions by @​nwoolmer in #​5623
• feat(sql): SQL hints for linear and indexed ASOF join algos by @​mtopolnik in #​6197
• feat(ilp): add gzip support to ILP/HTTP server by @​nwoolmer in #​6165
• feat(sql): speed-up queries with multiple IN predicates on indexed columns by @​jerrinot in #​6112
• perf(core): scale symbol capacity automatically by @​bluestreak01 in #​6149
• feat(sql): rnd_symbol_zipf() function for generating skewed symbol distributions by @​bluestreak01 in #​6217

New Contributors

• @​rmja made their first contribution in #​6107
• @​skytech9999 made their first contribution in #​6135
• @​vil02 made their first contribution in #​6209

Full Changelog: questdb/questdb@9.0.3...9.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.