Bump org.questdb:questdb from 9.0.3 to 9.1.0 in /modules/questdb

[dependabot]

Bumps org.questdb:questdb from 9.0.3 to 9.1.0.

Release notes

Sourced from org.questdb:questdb's releases.

9.1.0

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)

... (truncated)

Commits

• 138be6d [maven-release-plugin] prepare release 9.1.0
• e0c8064 chore(ui): upgrade web console to 1.1.3 (#6222)
• 5872d6f feat(sql): rnd_symbol_zipf() function for generating skewed symbol distribu...
• e783f08 chore(core): use std::isnan (#6209)
• bbfeecc chore(core): fix GLIBC smoke tests (#6216)
• d05da25 perf(core): scale symbol capacity automatically (#6149)
• a30ad8e test(core): fix fuzz tests to stop simulating failures on test cleanup. (#6215)
• 9ebcd3d feat(sql): speed-up queries with multiple IN predicates on indexed columns (#...
• c4af499 test(core): fix race conditions in tests that start multiple database instanc...
• 7eb19b9 feat(ilp): add gzip support to ILP/HTTP server (#6165)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)