Received authentication; waiting for backend start-up to finish.
Waiting for a response from the server.
Connection failed
Connection OK; waiting to send.
connect() needed.
Connection succeeded
Negotiating environment-driven parameter settings.
Negotiating SSL encryption.
Waiting for connection to be made.
Invalid OID constant
Flag for lo_creat, lo_open – open for reading
Flag for lo_creat, lo_open – open for writing
The server’s response was not understood.
Successful completion of a command returning no data.
Copy In (to server) data transfer started.
Copy Out (from server) data transfer started.
The string sent to the server was empty.
A fatal error occurred.
A nonfatal error (a notice or warning) occurred.
Async connection failed or was reset
Async connection succeeded
Async connection is waiting to read
Async connection is waiting to write
Successful completion of a command returning data
(such as a SELECT or SHOW).
If the error was associated with a specific table column, the name of the column. (When this field is present, the schema and table name fields identify the table.)
If the error was associated with a specific constraint, the name of the constraint. The table or domain that the constraint belongs to is reported using the fields listed above. (For this purpose, indexes are treated as constraints, even if they weren't created with constraint syntax.)
An indication of the context in which the error occurred. Presently this includes a call stack traceback of active procedural language functions and internally-generated queries. The trace is one entry per line, most recent rst.
If the error was associated with a specific datatype, the name of the datatype. (When this field is present, the schema name field provides the name of the datatype's schema.)
This is dened the same as the PG_DIAG_STATEMENT_POSITION eld, but it is used when the cursor position refers to an internally generated command rather than the one submitted by the client. The PG_DIAG_INTERNAL_QUERY eld will always appear when this eld appears.
The text of a failed internally-generated command. This could be, for example, a SQL query issued by a PL/pgSQL function.
an optional secondary error message carrying more detail about the problem. Might run to multiple lines.
an optional suggestion what to do about the problem. This is intended to differ from detail in that it offers advice (potentially inappropriate) rather than hard facts. Might run to multiple lines.
The primary human-readable error message (typically one line). Always present.
If the error was associated with a specific database object, the name of the schema containing that object, if any.
The severity; the field contents are ERROR, FATAL, or PANIC (in an error message), or WARNING, NOTICE, DEBUG, INFO, or LOG (in a notice message), or a localized translation of one of these. Always present.
The le name of the source-code location where the error was reported.
The name of the source-code function reporting the error.
The line number of the source-code location where the error was reported.
The SQLSTATE code for the error. The SQLSTATE code identies the type of error that has occurred; it can be used by front-end applications to perform specic operations (such as er- ror handling) in response to a particular database error. For a list of the possible SQLSTATE codes, see Appendix A. This eld is not localizable, and is always present.
A string containing a decimal integer indicating an error cursor position as an index into the original statement string. The rst character has index 1, and positions are measured in characters not bytes.
If the error was associated with a
specific table, the name of the table. (When this field is present, the schema name
field provides the name of the table's schema.)
Default error verbosity level (#set_error_verbosity)
Terse error verbosity level (#set_error_verbosity)
Verbose error verbosity level (#set_error_verbosity)
Connection not attempted (bad params).
Could not establish connection.
Server is accepting connections.
Server is alive but rejecting connections.
Transaction is currently active; query has been sent to the server, but not yet completed. (#transaction_status)
Transaction is currently idle (#transaction_status)
Transaction is currently idle, in a failed transaction block (#transaction_status)
Transaction is currently idle, in a valid transaction block (#transaction_status)
Transaction's connection is bad (#transaction_status)
Flag for lo_lseek – seek from current position
Flag for lo_lseek – seek from object end
Flag for lo_lseek – seek from object start