Vlad Ilyushchenko

hypothetically speaking if we have a single boundary we could fill to that only, open boundaries could be ignored in this context

I’m not sure, I tried to capture users feedback in the description. Perhaps there are outliers from the rule? Does adding index always bump correct version?

have a look at `WhereClauseParser`, this issue refers to the code, which recognises that designated, ordered timestamp column is being searched against a constant. Right now it picks up specific...

yes, sure

Could you drop index and recreate on 6.5.3 ?

you can drop it like so: https://questdb.io/docs/reference/sql/alter-table-alter-column-drop-index/ try without index first to make sure this is indeed index that's causing the problem you can add index like this: https://questdb.io/docs/reference/sql/alter-table-alter-column-add-index/

hey @Belair34 it is better late than never to reply! Sorry for the delay! This endpoint is meant to be read only. So it if it is SQL that is...

sure thing!

PR title can be more succinct 😀

FYI, on azul11 community the difference is less pronounced. Azul11 is slower than coretto 17