Skip to content

[Feedback] Page: /use-timescale/latest/hypercore/secondary-indexes/ #4187

Open
@cning-lmr

Description

@cning-lmr

Is it easy to find the information you need?

None

Are the instructions clear?

No

How could we improve the Timescale documentation site?

The query performance comparison between Execute a query on a regular hypertable and Execute a query on the same data segmented and ordered in the columnstore is not only unfair but also not correct:

  1. Why doesn't the first query on the regular hypertable use a time filter? The query planning is always less performant because of this reported issue [Bug]: Significant difference in buffers hit with OR clause affecting planning time timescaledb#7646
  2. The output of the second query is not correct obviously - the output has device_id and avg_disk_io columns which are not in the query

Metadata

Metadata

Labels

communityRaised by a community memberdocumentationImprovements or additions to documentationfeedbackSubmissions from the docs site feedback form

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions