Sven Klemm

This reposity contains some of the Dockerfiles for the images found at https://hub.docker.com/r/timescale/timescaledb. Not sure what the exact ask is. timescaledb-parallel-copy is not required to run timescaledb but may be...

As a workaround you can do the following: To get timescaledb to pushdown the result of a subselect you create an immutable function like so: ``` CREATE OR REPLACE FUNTION...

Hmm this seems to be misconception in the cache setup. We use the relid as cache key but a chunk can appear multiple times in a plan in different contexts.

This works for me on latest version.

@hardikm10 the reason for this behaviour is your configured orderby does not match the query orderby. orderby always implicitly includes any segmentby columns. Here is a workaround query that does...

There are 2 ways to optimize this. Number 1 is a special optimization for the limit 1 case as we can tell where to look for that immediately from metadata...

Hmm so in general you want to avoid last together with GROUP BY as we currently do not optimize that and you would be much better served by using LATERAL...

So there is some tiny overlap between last() and ORDER BY LIMIT because for the non-GROUP BY case we actually rewrite the query into ORDER BY time LIMIT but that...

@davidkohn88 this works for me, seeing that you are explicit about the operator classes did you by any chance use text_pattern_ops in your symbol index? text_pattern_ops indexes don't fulfill the...

@majozv You are using a very old version that is no longer supported. That specific error appearing in your logs should not happen on recent postgres and timescaledb versions.