Skip to content

[Feedback] #4552

@tpetry

Description

@tpetry

Is it easy to find the information you need?

None

Are the instructions clear?

None

How could we improve the Tiger Data documentation site?

The docs for continuous aggregates ([About continuous aggregates](https://docs.tigerdata.com/use-timescale/latest/continuous-aggregates/about-continuous-aggregates/)) state the following

When data older than the invalidation threshold is changed, the maximum and minimum timestamps of the changed rows is logged, and the values are used to determine which rows in the aggregation table need to be recalculated. This logging does cause some write load, but because the threshold lags behind the area of data that is currently changing, the writes are small and rare.

From my understanding (and talking to TigerData engineers) this statement is not entirely valid? Or is outdated? Only the buckets of continuous aggregate that are changed by modified rows are recalculated but not the entire range of bucket as indicated by the min/max note.

Metadata

Metadata

Assignees

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