V. EnterpriseDB Error Codes

All messages emitted by the EnterpriseDB server are assigned five-character error codes that follow the SQL standard conventions for "SQLSTATE" codes. Applications that need to know which error condition has occurred should usually test the error code, rather than looking at the textual error message. The error codes are less likely to change across EnterpriseDB releases, and are also not subject to change due to localization of error messages.

Note that some, but not all, of the error codes produced by EnterpriseDB are defined by the SQL standard; some additional error codes for conditions not defined by the standard have been invented or borrowed from other databases. In addition some error codes have been added to support Redwood compatibility of SPL. These are listed in Table 1.

According to the standard, the first two characters of an error code denote a class of errors, while the last three characters indicate a specific condition within that class. Thus, an application that does not recognize the specific error code may still be able to infer what to do by looking at the error class.

Table 1 lists all the error codes defined in EnterpriseDB. Some are not being used at present, but are defined in the SQL standard. The error classes have also been shown. For each error class, there is a "standard" error code having the last three characters 000. This code is used only for error conditions that fall within the class but do not have any more-specific assigned code.

The PL/pgSQL condition name for each error code is the same as the phrase shown in the table, with underscores substituted for spaces. For example, code 22012, DIVISION BY ZERO, has condition name DIVISION_BY_ZERO. Condition names can be written in either upper or lower case. The same condition names may also be used in SPL.

Note that PL/pgSQL does not recognize warning, as opposed to error, condition names; those are classes 00, 01, and 02.