GAUSS-00481 -- GAUSS-00490
GAUSS-00481: "parameter error in ParseHaListenAddr()"
SQLSTATE: XX000
Description: The function ParseHaListenAddr uses an incorrect parameter.
Solution: Find out the reason why the imported parameter pointer is null.
GAUSS-00482: "must be system admin to reset statistics counters"
SQLSTATE: 42501
Description: Only the system administrator has the permission to reset statistics counters.
Solution: Switch to a system administrator.
GAUSS-00483: "unrecognized reset target: '%s'"
SQLSTATE: 22023
Description: The target parameter to be reset is incorrect.
Solution: The parameter must be bgwriter.
GAUSS-00484: "could not read statistics message: %m"
SQLSTATE: XX000
Description: pgStat cannot read statistics messages.
Solution: Communication between threads in the database is abnormal. Contact technical support.
GAUSS-00485: "database hash table corrupted during cleanup --- abort"
SQLSTATE: XX000
Description: The hash table is corrupted during the database cleanup.
Solution: This is an internal database error. Contact technical support.
GAUSS-00486: "could not create sysauditor data transfer thread: %m"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-00487: "could not create pipe for sysaudit: %m"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-00488: "could not write to audit file: %m"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-00489: "set-valued function called in context that cannot accept a set"
SQLSTATE: 0A000
Description: The function that is expected to return a result set fails to return a result set.
Solution: Ensure that this function is defined to return a result set.
GAUSS-00490: "materialize mode required, but it is not allowed in this context"
SQLSTATE: 0A000
Description: The returned tuplestore is not supported in this context.
Solution: Change the type of the returned value.
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