TSBS version: commit ID 56292c590836954593f5ab8b9434592aa77aa4d2
Hi,
We have an issue when executing queries generated by calling tsbs_generate_queries --timescale-use-json=true .... At the execution, we face various errors:
When executing queries generated with the query type avg-load and high-load, the error message is:
panic: ERROR: operator does not exist: double precision / jsonb (SQLSTATE 42883)goroutine 9 [running]:
github.com/timescale/tsbs/pkg/query.(*BenchmarkRunner).processorHandler(0xc00012c6e0, 0xc000026ed0, 0xc0000788c0, 0xc80440, 0x9f1140, 0xc000191100, 0x2)
/app/tsbs/src/github.com/timescale/tsbs/pkg/query/benchmarker.go:196 +0x293
created by github.com/timescale/tsbs/pkg/query.(*BenchmarkRunner).Run
/app/tsbs/src/github.com/timescale/tsbs/pkg/query/benchmarker.go:156 +0x206
When executing queries generated with the query type avg-vs-projected-fuel-consumption, the error message is:
panic: ERROR: function avg(text) does not exist (SQLSTATE 42883)goroutine 22 [running]:
github.com/timescale/tsbs/pkg/query.(*BenchmarkRunner).processorHandler(0xc00014e630, 0xc00011ce00, 0xc0001008c0, 0xc80440, 0x9f1140, 0xc0001b70f0, 0x2)
/app/tsbs/src/github.com/timescale/tsbs/pkg/query/benchmarker.go:196 +0x293
created by github.com/timescale/tsbs/pkg/query.(*BenchmarkRunner).Run
/app/tsbs/src/github.com/timescale/tsbs/pkg/query/benchmarker.go:156 +0x206
Is it a known issue with the JSONB use case? Should we just skip these query types for the time being in the JSONB use case or do you have a workaround we could apply?
TSBS version: commit ID 56292c590836954593f5ab8b9434592aa77aa4d2
Hi,
We have an issue when executing queries generated by calling
tsbs_generate_queries --timescale-use-json=true ...
. At the execution, we face various errors:When executing queries generated with the query type
avg-load
andhigh-load
, the error message is:When executing queries generated with the query type
avg-vs-projected-fuel-consumption
, the error message is:Is it a known issue with the JSONB use case? Should we just skip these query types for the time being in the JSONB use case or do you have a workaround we could apply?
Thanks a lot for this open source tool :)