questdb.io
questdb.io copied to clipboard
Update O3 documentation
We've to update O3 documentation and explicitly state that we DON'T support O3 for non-partitioned tables . If O3 doesn't make sense for such tables then maybe we should force users to use partitioning on tables with designated timestamp even .
Potential location: Configuring commit lag of out-of-order (O3) data Capacity planning> Storage and filesystem > Partitioning