This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Store metrics using explicit schema #165
Labels
enhancement
New feature or request
refactoring
Something done as it should've been done from the start
sinks
Where and how to store monitored data
Milestone
In pgw2 data and tags are stored as jsonb. This duplicates schema information in every row, giving bad storage efficiency for uncompressed data. It also defeats timeseries compression mechanisms for compressed data. Additionally, any access to data needs to decompress the whole document instead of accessing just the necessary column, which is very important for columnar storage.
Storing series metadata (e.g. full query text) out-of-line in a separate table might also be a good idea.
TBD: measurements on real world data
The text was updated successfully, but these errors were encountered: