ANALYZE | ANALYSE

Function

ANALYZE collects statistics about ordinary tables in a database, and stores the results in the PG_STATISTIC system catalog. The execution plan generator uses these statistics to determine which one is the most effective execution plan.

If no parameter is specified, ANALYZE analyzes each table and partitioned table in the current database. You can also specify the table_name, column, and partition_name parameters to restrict the analysis to a specific table, column, or partitioned table.

ANALYZE | ANALYSE VERIFY is used to check whether data files of common tables (row-store and column-store tables) in a database are damaged.

Precautions

• Non-temporary tables cannot be analyzed in an anonymous block, transaction block, function, or stored procedure. Temporary tables in a stored procedure can be analyzed but their statistics updates cannot be rolled back.
• The ANALYZE VERIFY operation is used to detect abnormal scenarios. The RELEASE version is required. In the ANALYZE VERIFY scenario, remote read is not triggered. Therefore, the remote read parameter does not take effect. If the system detects that a page is damaged due to an error in a key system table, the system directly reports an error and does not continue the detection.
• With no table specified, ANALYZE processes all the tables that the current user has permission to analyze in the current database. With tables specified, ANALYZE processes only the specified tables.
• To perform ANALYZE operation to a table, you must be a table owner or a user granted the VACUUM permission on the table. By default, the system administrator has this permission. However, database owners are allowed to ANALYZE all tables in their databases, except shared catalogs. (The restriction for shared catalogs means that a true database-wide ANALYZE can only be executed by the system administrator). ANALYZE skips tables on which users do not have permissions.

Syntax

• Collect statistics information about a table.

  { ANALYZE | ANALYSE } [ VERBOSE ]
      [ table_name [ ( column_name [, ...] ) ] ];

• Collect partition statistics information about a partitioned table. This syntax is not supported currently.

  { ANALYZE | ANALYSE } [ VERBOSE ]
      table_name [ ( column_name [, ...] ) ] PARTITION ( patrition_name ) ;

  

  An ordinary partitioned table supports the syntax but not the function of collecting statistics about specified partitions.

Parameter Description

• VERBOSE

  Enables the display of progress messages.

  

  If VERBOSE is specified, ANALYZE displays the progress information, indicating the table that is being processed. Statistics about tables are also displayed.

• table_name

  Specifies the name (possibly schema-qualified) of a specific table to analyze. If omitted, all regular tables (but not foreign tables) in the current database are analyzed.

  Currently, you can use ANALYZE to collect statistics only from row-store tables and column-store tables.

  Value range: an existing table name

• column_name, column_1_name, column_2_name

  Specifies the name of a specific column to analyze. All columns are analyzed by default.

  Value range: an existing column name

• partition_name

  Assumes the table is a partitioned table. You can specify partition_name following the keyword PARTITION to analyze the statistics of this table. Currently, ANALYZE can be performed on partitioned tables, but statistics of specified partitions cannot be analyzed.

  Value range: a partition name of a table

• index_name

  Specifies the name of the specific index table to be analyzed (possibly schema-qualified).

  Value range: an existing table name

• FAST|COMPLETE

  For a row-store table, the FAST mode verifies the CRC and page header of the row-store table. If the verification fails, an alarm is generated. In COMPLETE mode, the pointer and tuple of the row-store table are parsed and verified. For a column-store table, the FAST mode verifies the CRC and magic of the column-store table. If the verification fails, an alarm is generated. In COMPLETE mode, the CU of the column-store table is parsed and verified.

• CASCADE

  In CASCADE mode, all indexes of the current table are verified.

Examples

-- Create a table.

openGauss=# CREATE TABLE customer_info
(
WR_RETURNED_DATE_SK       INTEGER                       ,
WR_RETURNED_TIME_SK       INTEGER                       ,
WR_ITEM_SK                INTEGER               NOT NULL,
WR_REFUNDED_CUSTOMER_SK   INTEGER
)
;

-- Create a partitioned table.

openGauss=# CREATE TABLE customer_par
(
WR_RETURNED_DATE_SK       INTEGER                       ,
WR_RETURNED_TIME_SK       INTEGER                       ,
WR_ITEM_SK                INTEGER               NOT NULL,
WR_REFUNDED_CUSTOMER_SK   INTEGER
)
PARTITION BY RANGE(WR_RETURNED_DATE_SK)
(
PARTITION P1 VALUES LESS THAN(2452275),
PARTITION P2 VALUES LESS THAN(2452640),
PARTITION P3 VALUES LESS THAN(2453000),
PARTITION P4 VALUES LESS THAN(MAXVALUE)
)
ENABLE ROW MOVEMENT;

-- Run ANALYZE to update statistics.

openGauss=# ANALYZE customer_info;
openGauss=# ANALYZE customer_par;

-- Run the ANALYZE VERBOSE statement to update statistics and display table information.

openGauss=# ANALYZE VERBOSE customer_info;
INFO:  analyzing "cstore.pg_delta_3394584009"(cn_5002 pid=53078)
INFO:  analyzing "public.customer_info"(cn_5002 pid=53078)
INFO:  analyzing "public.customer_info" inheritance tree(cn_5002 pid=53078)
ANALYZE

If any environment-related fault occurs, check the logs of the primary node of the database.

-- Delete the table.

openGauss=# DROP TABLE customer_info;
openGauss=# DROP TABLE customer_par;