检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
The sample data is stored in an OBS bucket accessible to all authenticated cloud users. Note that <obs_bucket_name> in the following statement indicates the OBS bucket name. Only some regions are supported.
Local disks are used as the query cache of OBS data. Row-store data is still stored in local disks of compute nodes. Advantage Data is stored locally on compute nodes, providing high performance.
Default value: off acceleration_with_compute_pool Parameter description: Specifies whether to use the computing resource pool for acceleration when OBS is queried.
Default value: off acceleration_with_compute_pool Parameter description: Specifies whether to use the computing resource pool for acceleration when OBS is queried.
Excellent query performance High-quality query plans and efficient execution engines Precise load management methods Real-Time Write DWS 3.0 utilizes the H-Store storage engine to store micro-batch data locally and syncs it to OBS at regular intervals.
Notes and Constraints Manually created snapshots can be backed up to OBS or NFS. To create a snapshot of a cluster, ensure that the cluster is in Available, To be restarted, or Unbalanced state.
pg_total_relation_size can specify the OID or name of a table or compressed table, and then return the data in bytes and the sizes of all related indexes and compressed tables. pg_obs_file_size(regclass) Description: This function obtains the CU file size, file name, and bucket ID stored on OBS
Snapshots whose backup device is OBS can be used to restore one or multiple tables. Restoration can be performed only if the snapshot and the cluster are both in the Available state. A table in a read-only cluster cannot be restored.
Use the default OBS tablespace.
Data masking policies can be created for regular tables and non-EXTERNAL-SCHEMA foreign tables (such as OBS, HDFS, GDS, and foreign tables for coordinated analysis), but not for system catalogs, EXTERNAL SCHEMA foreign tables, temporary tables, UNLOGGED tables, views, or functions
If the manual snapshots are still retained after the cluster is deleted and the total snapshot size exceeds the free space, the excess part will be billed based on the OBS billing rate.
cluster_id String Cluster ID count Integer Total number Table 3 AuditDumpRecord Parameter Type Description cluster_id String Cluster ID exector_time String Execution time begin_time String Start time end_time String End time bucket_name String Bucket name location_prefix String OBS
- Cold Data Store data in separate OBS buckets, which are billed on a pay-per-use basis. - Nodes Specify the number of nodes in the cluster. The number of nodes ranges from 3 to 256. 3 Total Display the cluster's total capacity.
The cold_tablespace and storage_policy parameters of ALTER RESET cannot be used in OBS multi-temperature tables, and COLVERSION cannot be changed to 1.0 for such tables. You can change a column-store table whose COLVERSION parameter is 2.0 to an OBS multi-temperature table.
* 2,3,4,5,6,7", "backup_type": "increment", "backup_level": "cluster", "next_fire_time": "1667213760000", "update_time": "2022-10-31T02:54:54" } ], "device_name": "obs", "server_ips": null, "server_port": null, "backup_param": "" } SDK Sample
Snapshots are stored in the storage space of Object Storage Service (OBS). snapshot restoration A snapshot can be used to restore a cluster to a newly created one that has the same specifications. Currently, you can restore a cluster only to a new one.
Type: USERSET Value range: enumerated values 0: The size of the database is directly estimated based on the OBS bucket. 1: The size of the entire database is normally calculated in regular mode.
Use cstore_buffers to specify the cache of ORC, Parquet, or CarbonData metadata and data for OBS or HDFS foreign tables. The metadata cache size should be 1/4 of cstore_buffers and not exceed 2 GB.
Use cstore_buffers to specify the cache of ORC, Parquet, or CarbonData metadata and data for OBS or HDFS foreign tables. The metadata cache size should be 1/4 of cstore_buffers and not exceed 2 GB.
Type: USERSET Value range: enumerated values 0: The size of the database is directly estimated based on the OBS bucket. 1: The size of the entire database is normally calculated in regular mode.