Error Message Severities¶
The error message severities are:
Comparative to severities in PostgreSQL,
- TRACE, INFO and WARNING are equivalent to PSQL INFO.
- DEBUG is equivalent to PSQL DEBUG.
- ERROR is equivalent to PSQL ERROR.
- FATAL is equivalent to PSQL FATAL.
TRACE, INFO and DEBUG are used to get helpful output for debugging. WARNING indicates strange behavior, invalid input or bad configuration. ERROR messages cause the currently executing query to fail. FATAL messages cause the program to halt and produce a core file.
Errors in Octo are of the form
ERR_<error>. The errors are detailed below, in alphabetical order.
This error means that the generated routines and the database seem to be out of sync.
A user attempted to use a feature that has not been implemented yet, generating an error.
There was an error intializing the scanner used to parse provided input. Please contact your YottaDB support channel.
This message indicates that an attempt to read a PSQL message from the wire failed because the provided size was too small. This likely represents an error with the client attempting to connect to rocto. Please contact your YottaDB support channel.
This indicates an issue writing a PSQL message to the wire. Please contact your YottaDB support channel.
This message is generated when the flow of control is leaving a function and is valuable to Octo developers to debug behavior.
This error indicates that the schema for table dddd did not have the correct number of keys. To solve this issue, the schema needs to be corrected.
This message indicates that the table has multiple KEY NUM elements with the same number, and that the source schema needs to be corrected.
This error is generated when Octo failed to generate the filename hash for the plan.
This error is generated when the plan produced by the optimizer does not seem correct. Please contact your YottaDB support channel.
This error is generated when a table was created without specifying a primary key.
This is a debug message useful when debugging the rocto server PSQL protocol implementation and indicates that a message of a particular type is being processed.
This message is used to inform the rocto server about the session variables being passed from the client to the server during initialization.
This is a debug message useful when debugging the rocto server PSQL protocol implementation and indicates that a message of the specified format was read from the wire.
This error indicates that a PSQL wire protocol message exceeded the maximum size of messages which can be read by rocto. Please contact your YottaDB support channel.
This is a debug message useful when debugging the rocto server PSQL protocol implementation and indicates that a message of the specified format was written to the wire.
An unknown state was reached, which generated an error. Please contact your YottaDB support channel.
This error is generated when an unknown message type was received from the front end. Please contact your YottaDB support channel.
Errors in Rocto are of the form
ERR_ROCTO_<error>. The errors are detailed below, in alphabetical order.
PostgreSQL Error Codes Used¶
Octo uses a few PostgreSQL Error Codes.
List of PostgreSQL error codes defined and used in Octo:
|Error Code||Condition Name|
|Class 00 — Successful Completion|
|Class 08 — Connection Exception|
|Class 26 — Invalid SQL Statement Name|
|Class 42 — Syntax Error or Access Rule Violation|