Sven Klemm

> It fixes the segfault but won't it create some perf regression? Potentially yes. Ideally we can reenable this in followup PR after we fix OR processing.

Boiled down query: ``` SELECT queryid, lag(total_exec_time) OVER (PARTITION BY queryid) FROM public.stat_statements WHERE db_id = 7401 AND observed >= now() - interval '1 day' LIMIT 10; ``` Resolving the...

The linked snippet clearly shows the adaptive chunk test throwing the error instead of compression_indexscan

The difference seems to be Nested Loop Join vs Hash Join. Did you intentionally choose to use timestamp without timezone here? This introduces casts in this query which make the...

> > Did you intentionally choose to use timestamp without timezone here? > > Yes. To eliminate variables, I wanted the data type to be consistent between the relative and...

Which timescaledb version is that? Could you provide a self-contained producer or a stacktrace. From the provided information it is hard to reproduce the problem.

When doing major pg version upgrade source and destination version are required to be identical

Statistics are tracked on a chunk level and do not propagate to the hypertable. The stats present on the hypertable are most likely from before turning it in hypertable since...

Could you check what opexpr->args is in the coredump and maybe all the other fields of opexpr too to see what might be wrong. This should be fixed in main...

Hello, thx for the update i'll label the issue as waiting for your input.