Null for minTimestamp, maxTimestamp and rowCount

Community
1

image
image1872×851 61.3 KB

These columns should have values, why is it not working properly?

2

Additional columns will only show data for tables created with the V2 sequencer format. The format has existed for a while, but it isn’t the default yet. It’s been fully tested for years, so it’s safe to enable if you need it, and it also reduces
disk space usage.

To enable, add this to server.conf:

cairo.default.sequencer.part.txn.count=50000

Any value >= 1 switches new tables to V2 (the value is the number of txns per sequencer log chunk; 0 keeps V1). Then restart QuestDB. The new format only applies to tables created after the config switch — existing tables stay on V1.

Alternatively, you can query sys.telemetry_wal, which already records minTimestamp, maxTimestamp and rowCount for committed events (event code 109, WAL_TXN_COMMITTED) regardless of sequencer format. For example:

SELECT created, tableId, walId, seqTxn, rowCount, minTimestamp, maxTimestamp
  FROM sys.telemetry_wal
  WHERE event = 109;
3

Thank You, it works.