GAUSS-05161 -- GAUSS-05170

AUSS-05161: “can not open pg_database”

SQLSTATE: 58000

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05162: “count is invalid, count:%d, tmpCount:%d”

SQLSTATE: 58000

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05163: “must be system admin or operator admin in operation mode to manage pooler”

SQLSTATE: 42501

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05164: “pg_pool_ping cannot run inside a transaction block”

SQLSTATE: 25001

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05165: “invalid input/output buffer in node handle”

SQLSTATE: 53200

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05166: “out of memory for node handles”

SQLSTATE: 53200

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05167: “coordinator cannot identify itself”

SQLSTATE: XX000

Description: An internal system error occurs. The pgxc_node system catalog may have been damaged or the user has modified the pgxc_node_name parameter of the failed node.

Solution: It is not recommended that users modify the pgxc_node_name parameter. If the fault is caused by incorrect parameter modification, perform the following operations: 1. Enable the CN in restore mode. Obtain the nodename by querying the pgxc_node system table. Restore the configuration parameter based on the nodename obtained. 2. Restore the configuration parameter using the standard log name of this instance generated in OM mode. "

GAUSS-05168: “message len is too short”

SQLSTATE: 22023

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05169: “conn cursor overflow”

SQLSTATE: 22023

Description: Internal system error.

Solution:Contact technical support.

GAUSS-05170: “Invalid Datanode number”

SQLSTATE: 53200

Description: Internal system error.

Solution:Contact technical support.