Sets the chunk_time_interval
on a hypertable. The new interval is used
when new chunks are created, and time intervals on existing chunks are
not changed.
Name | Type | Description |
---|---|---|
hypertable | REGCLASS | Hypertable or continuous aggregate to update interval for |
chunk_time_interval | See note | Event time that each new chunk covers |
The valid types for the chunk_time_interval
depend on the type used for the
hypertable time
column:
time column type | chunk_time_interval type | Time unit |
---|---|---|
TIMESTAMP | INTERVAL | days, hours, minutes, etc |
INTEGER or BIGINT | microseconds | |
TIMESTAMPTZ | INTERVAL | days, hours, minutes, etc |
INTEGER or BIGINT | microseconds | |
DATE | INTERVAL | days, hours, minutes, etc |
INTEGER or BIGINT | microseconds | |
SMALLINT | SMALLINT | The same time unit as the time column |
INT | INT | The same time unit as the time column |
BIGINT | BIGINT | The same time unit as the time column |
For more information, see the create_hypertable
section.
TEXT | Description | |
---|---|---|
dimension_name | REGCLASS | The name of the time dimension to set the number of partitions for |
You need to use dimension_name
argument only if your hypertable has multiple
time dimensions.
For a TIMESTAMP column, set chunk_time_interval
to 24 hours:
SELECT set_chunk_time_interval('conditions', INTERVAL '24 hours');SELECT set_chunk_time_interval('conditions', 86400000000);
For a time column expressed as the number of milliseconds since the
UNIX epoch, set chunk_time_interval
to 24 hours:
SELECT set_chunk_time_interval('conditions', 86400000);
Keywords
Found an issue on this page?Report an issue or Edit this page in GitHub.