DB_IND_SUBPARTITIONS
DB_IND_SUBPARTITIONS displays partition information about local indexes of level-2 partitioned table accessible to the current user (excluding global indexes of partitioned tables). It is accessible to all users. This view exists in both PG_CATALOG and SYS schema.
Name |
Type |
Description |
---|---|---|
index_owner |
character varying(64) |
Owner name of the partitioned table index to which an index partition belongs. |
index_name |
character varying(64) |
Index name of the partitioned table index to which an index partition belongs. |
partition_name |
character varying(64) |
Name of the level-1 partition where an index is located. |
subpartition_name |
character varying(64) |
Name of the level-2 partition where an index is located. |
def_tablespace_name |
name |
Tablespace name of an index partition. |
high_value |
text |
Limit of the partition corresponding to an index partition. |
index_partition_usable |
boolean |
Specifies whether an index partition is available.
|
schema |
character varying(64) |
Schema of the partitioned table index to which an index partition belongs. |
high_value_length |
integer |
Character length of the limit of the partition corresponding to an index partition. |
partition_position |
numeric |
Position of an index partition in the index. |
subpartition_position |
numeric |
Position of the level-2 partition in the partition. |
status |
character varying(8) |
Specifies whether the index partition is available. |
tablespace_name |
name |
Tablespace name of an index partition. |
pct_free |
numeric |
Minimum percentage of available space in a block. |
ini_trans |
numeric |
Initial number of transactions. The default value is 4. The value is NULL for non-Ustore partitioned tables. |
max_trans |
numeric |
Maximum number of transactions. The default value is 128. The value is NULL for non-Ustore partitioned tables. |
initial_extent |
numeric |
Not supported. Its value is NULL. |
next_extent |
numeric |
Not supported. Its value is NULL. |
min_extent |
numeric |
Not supported. Its value is NULL. |
max_extent |
numeric |
Not supported. Its value is NULL. |
max_size |
numeric |
Not supported. Its value is NULL. |
pct_increase |
numeric |
Not supported. Its value is NULL. |
freelists |
numeric |
Not supported. Its value is NULL. |
freelist_groups |
numeric |
Not supported. Its value is NULL. |
logging |
character varying(7) |
Specifies whether changes to an index are recorded. |
compression |
character varying(13) |
Compression type used for level-2 partitions. |
blevel |
numeric |
Not supported. Its value is NULL. |
leaf_blocks |
numeric |
Not supported. Its value is NULL. |
distinct_keys |
numeric |
Not supported. Its value is NULL. |
avg_leaf_blocks_per_key |
numeric |
Not supported. Its value is NULL. |
avg_data_blocks_per_key |
numeric |
Not supported. Its value is NULL. |
clustering_factor |
numeric |
Sequence of a row in the table based on the value of the index. You need to run the analyze command to collect statistics. |
num_rows |
numeric |
Number of rows in a level-2 partition. You need to run the vacuum command to collect statistics. |
sample_size |
numeric |
Not supported. Its value is NULL. |
last_analyzed |
timestamp with time zone |
Last date when the partition was analyzed. |
buffer_pool |
character varying(7) |
Buffer pool of a level-2 partition. |
flash_cache |
character varying(7) |
Not supported. Its value is NULL. |
cell_flash_cache |
character varying(7) |
Not supported. Its value is NULL. |
user_stats |
character varying(3) |
Not supported. Its value is NULL. |
global_stats |
character varying(3) |
Not supported. Its value is NULL. |
interval |
character varying(3) |
Specifies whether the partition is a partition in an interval partitioned table. |
segment_created |
character varying(3) |
Specifies whether an index partition segment has been created. |
domidx_opstatus |
character varying(6) |
Not supported. Its value is NULL. |
parameters |
character varying(1000) |
Not supported. Its value is NULL. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot