Dario Heinisch

Thanks my friend. I am currently slammed with work (postgres -> clickhouse migration :D ) but looking to do https://github.com/plausible/chto/issues/37 over the weekend.

I have taken another look, look at the queries: ```elixir false 16:18:06.013 [debug] QUERY OK source="products" db=2.9ms idle=191.2ms SELECT true FROM "products" AS p0 WHERE (p0."approved_at" = {$0:DateTime}) LIMIT 1...

I think `final` still has some issues because it cannot move always the `where` clause to `prewhere`. See https://github.com/ClickHouse/ClickHouse/issues/31411 So I would advise to not use/promote the usage of `final`...

Really? Do you have an example? I am curious because I cannot think of an example maybe because I never encountered such a situation

You can use aggregating functions - `sum`, `avg`, `argMaxMerge`, etc. - + group by to have the same effect as your final query

But can't you just do ```sql select id, started_at, max(disconnected_at) as disconnected_at, max(user_responded_at) as user_responded_at, groupArrayArray(properties) as properties from group by id, started_at ``` Maybe I am not really following....

It depends on your use case. If you have a small dataset final should be fine. If you have a larger dataset final should be avoided. If you don't run...

I mean 0.584 isn't bad depending on use case but also I dont see the full query & table so cannot say whether the query without final is performant written...

The case is not clear because I don't see the table definition and the queries you used that result in that huge performance diff Edit: I am not against the...

I have not but the reason I did it is because I found the IV calculation of Jaeckel more accurate when comparing it with my local brokers. The rust one...