GAUSS-04071 -- GAUSS-04080

GAUSS-04071: "not enough elements in RWConflictPool to record a read/write conflict"

SQLSTATE: 53200

Description: The RWConflictPool memory is insufficient and cannot record more read and write conflicts.

Solution: Set max_connections or try again in a new transaction.

GAUSS-04072: "not enough elements in RWConflictPool to record a potential read/write conflict"

SQLSTATE: 53200

Description: The RWConflictPool memory is insufficient and cannot record more read and write conflicts.

Solution: Set max_connections or try again in a new transaction.

GAUSS-04073: "not enough shared memory for elements of data structure '%s' (%lu bytes requested)"

SQLSTATE: 53200

Description: No sufficient memory is available to initialize PredXactList.

Solution: Check whether the available system memory is sufficient.

GAUSS-04074: "cannot use serializable mode in a hot standby"

SQLSTATE: 0A000

Description: Hot standby cannot be set to the serialized mode.

Solution: Set default_transaction_isolation to repeatable read.

GAUSS-04075: "a snapshot-importing transaction must not be READ ONLY DEFERRABLE"

SQLSTATE: 0A000

Description: READ ONLY DEFERRABLE cannot be imported into snapshots.

Solution: Modify the transaction level.

GAUSS-04076: "could not serialize access due to read/write dependencies among transactions"

SQLSTATE: 40001

Description: The read and write operations conflict in serializable mode.

Solution: Try again.

GAUSS-04077: "unrecognized return value from HeapTupleSatisfiesVacuum: %u"

SQLSTATE: XX000

Description: The returned value of HeapTupleSatisfiesVacuum cannot be identified.

Solution: Contact technical support.

GAUSS-04078: "deadlock seems to have disappeared"

SQLSTATE: XX000

Description: The deadlock abnormally disappears.

Solution: Contact technical support.

GAUSS-04079: "inconsistent results during deadlock check"

SQLSTATE: XX000

Description: The deadlock detection results are inconsistent.

Solution: Contact technical support.

GAUSS-04080: "deadlock detected"

SQLSTATE: 40P01

Description: A deadlock occurred. Generally, this is because service scheduling is improper and a large number of operations are performed in a certain period.

Solution: Check the pg_stat_activity view and find the ID of the process that causes the deadlock. Run SELECT pg_cancel_backend($pid); to terminate the deadlock thread.