[Feedback] Unclear compression practice from the Cryptocurrency - part 1 tutorial

[shawnkoh]

Is it easy to find the information you need?

Yes

Are the instructions clear?

No

How could we improve the Timescale documentation site?

In Cryptocurrency - part 1 tutorial , readers were tasked to compress the transactions table.

ALTER TABLE transactions 
SET (
    timescaledb.compress, 
    timescaledb.compress_segmentby='block_id', 
    timescaledb.compress_orderby='time DESC'
);

The following warning appears.

WARNING:  column "hash" should be used for segmenting or ordering

From what I understand, the warning arises because the compression process ignores the unique index.

Is there a "best practice" for handling situations like this where uncompressed data should enforce uniqueness?

[github-actions[bot]]

Thank you for the report. We welcome documentation contributions!

• For information about how to propose a change, see the contributing guide in our GitHub repository.
• For information on style and word usage, see the style guide