range_start and
range_end are set. Otherwise, if the primary dimension type is integer based,
range_start_integer and range_end_integer are set.
Samples
Get information about the s of a .Dimension builder
by_range was introduced in 2.13.
The chunk_creation_time metadata was introduced in 2.13.Returns
| Name | Type | Description |
|---|---|---|
hypertable_schema | TEXT | Schema name of the hypertable |
hypertable_name | TEXT | Table name of the hypertable |
chunk_schema | TEXT | Schema name of the chunk |
chunk_name | TEXT | Name of the chunk |
primary_dimension | TEXT | Name of the column that is the primary dimension |
primary_dimension_type | REGTYPE | Type of the column that is the primary dimension |
range_start | TIMESTAMP WITH TIME ZONE | Start of the range for the ‘s dimension |
range_end | TIMESTAMP WITH TIME ZONE | End of the range for the ‘s dimension |
range_start_integer | BIGINT | Start of the range for the ‘s dimension, if the dimension type is integer based |
range_end_integer | BIGINT | End of the range for the ‘s dimension, if the dimension type is integer based |
is_compressed | BOOLEAN | Is the data in the compressed? Note that for distributed s, this is the cached compression status of the on the access node. The cached status on the access node and data node is not in sync in some scenarios. For example, if a user compresses or decompresses the on the data node instead of the access node, or sets up compression policies directly on data nodes. Use chunk_compression_stats() function to get real-time compression status for distributed s. |
chunk_tablespace | TEXT | Tablespace used by the |
data_nodes | ARRAY | Nodes on which the is replicated. This is applicable only to s for distributed s |
chunk_creation_time | TIMESTAMP WITH TIME ZONE | The time when this was created for data addition |