Jaromir Hamala

@ideoma yes, totally. all changes in this PR - except the code for the detector itself - are actual leak fixes. I want to jump on this right after https://github.com/questdb/questdb/pull/2184...

that's a weird location, isnt it? as a user I am confused by this.

good news: it builds fine on ARM64, which is definitely more relevant than ARM32. ``` [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 06:38 min (Wall Clock) ```

@Iqop that's fantastic, thanks for sharing! may I ask you what's your use-case for Jet on ARM32? If you are not comfortable talking about it then feel free to ignore...

+1 for #2. Otherwise as a user I have to guess where to click. "large vs small" is not a great differentiator as these terms are very relative.

Just a note I do not want to forget. There was one more hiccup after implementing `pg_catalog.pg_tables`: I created a target table in QuestDB called `decodable`, but Decodable complained it...

there is already an open issue related to the schema thing: https://github.com/questdb/questdb/issues/1577

Thanks for a super-fast response! I understand it's not a priority at all. I don't see any sensible use-case. I stumbled upon it while testing my implementation of https://github.com/questdb/questdb/issues/1818 and...

Hello Peter, nice to you see here! :) You are right, it does looks rather suspicious. I'm sure we will have a look at this at some point. I'm going...

related to https://github.com/questdb/questdb/issues/1227 thanks to @bziobrowski for spotting it.