module PG::Constants

Waiting for connection attempt to be started. Available since PostgreSQL-17.

Received authentication; waiting for backend startup.

Waiting for a response from the server.

Connection failed

Checking if server is in standby mode. Available since PostgreSQL-14.

Checking target server properties. Available since PostgreSQL-13.

Checking if session is read-write. Available since PostgreSQL-10.

Consuming any extra messages. Available since PostgreSQL-10.

Negotiating GSSAPI. Available since PostgreSQL-12.

Connection OK; waiting to send.

Internal state - PG.connect() needed.

Connection succeeded

This state is no longer used.

Negotiating SSL encryption.

Waiting for connection to be made.

PostgreSQL compiled in default port

Invalid OID constant

Flag for Connection#lo_creat, Connection#lo_open – open for reading

Flag for Connection#lo_creat, Connection#lo_open – open for writing

Result#result_status constant - The server’s response was not understood.

Result#result_status constant - Successful completion of a command returning no data.

Result#result_status constant - Copy In/Out data transfer in progress.

Result#result_status constant - Copy In (to server) data transfer started.

Result#result_status constant - Copy Out (from server) data transfer started.

Result#result_status constant - The string sent to the server was empty.

Result#result_status constant - A fatal error occurred.

Result#result_status constant - A nonfatal error (a notice or warning) occurred.

Result#result_status constant - The PG::Result represents a pipeline that has received an error from the server.

Connection#get_result must be called repeatedly, and each time it will return this status code until the end of the current pipeline, at which point it will return PG::PGRES_PIPELINE_SYNC and normal processing can resume.

Result#result_status constant - The PG::Result represents a synchronization point in pipeline mode, requested by Connection#pipeline_sync.

This status occurs only when pipeline mode has been selected.

Async connection failed or was reset

Async connection succeeded

Async connection is waiting to read

Async connection is waiting to write

Result#result_status constant - Single tuple from larger resultset.

Result#result_status constant - tuple chunk from larger resultset.

Result#result_status constant - Successful completion of a command returning data (such as a SELECT or SHOW).

Result#result_error_field argument constant

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.)

Result#result_error_field argument constant

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.)

Result#result_error_field argument constant

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 first.

Result#result_error_field argument constant

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.)

Result#result_error_field argument constant

This is defined the same as the PG_DIAG_STATEMENT_POSITION field, 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 field will always appear when this field appears.

Result#result_error_field argument constant

The text of a failed internally-generated command. This could be, for example, a SQL query issued by a PL/pgSQL function.

Result#result_error_field argument constant

Detail: an optional secondary error message carrying more detail about the problem. Might run to multiple lines.

Result#result_error_field argument constant

Hint: 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.

Result#result_error_field argument constant

The primary human-readable error message (typically one line). Always present.

Result#result_error_field argument constant

If the error was associated with a specific database object, the name of the schema containing that object, if any.

Result#result_error_field argument constant

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.

Result#result_error_field argument constant

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). This is identical to the PG_DIAG_SEVERITY field except that the contents are never localized.

Result#result_error_field argument constant

The file name of the source-code location where the error was reported.

Result#result_error_field argument constant

The name of the source-code function reporting the error.

Result#result_error_field argument constant

The line number of the source-code location where the error was reported.

Result#result_error_field argument constant

The SQLSTATE code for the error. The SQLSTATE code identifies the type of error that has occurred; it can be used by front-end applications to perform specific operations (such as error handling) in response to a particular database error. For a list of the possible SQLSTATE codes, see Appendix A. This field is not localizable, and is always present.

Result#result_error_field argument constant

A string containing a decimal integer indicating an error cursor position as an index into the original statement string.

The first character has index 1, and positions are measured in characters not bytes.

Result#result_error_field argument constant

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.)

Error verbosity level ( Connection#set_error_verbosity ). The DEFAULT mode produces messages that include the above plus any detail, hint, or context fields (these might span multiple lines).

Error verbosity level ( Connection#set_error_verbosity ). The SQLSTATE mode includes only the error severity and the SQLSTATE error code, if one is available (if not, the output is like TERSE mode).

Available since PostgreSQL-12.

Error verbosity level ( Connection#set_error_verbosity ). In TERSE mode, returned messages include severity, primary text, and position only; this will normally fit on a single line.

Error verbosity level ( Connection#set_error_verbosity ). The VERBOSE mode includes all available fields.

Connection not attempted (bad params).

Could not establish connection.

Server is accepting connections.

Server is alive but rejecting connections.

See Connection#set_error_context_visibility

See Connection#set_error_context_visibility

See Connection#set_error_context_visibility

Transaction is currently active; query has been sent to the server, but not yet completed. ( Connection#transaction_status )

Transaction is currently idle ( Connection#transaction_status )

Transaction is currently idle, in a failed transaction block ( Connection#transaction_status )

Transaction is currently idle, in a valid transaction block ( Connection#transaction_status )

Transaction’s connection is bad ( Connection#transaction_status )

Connection#pipeline_status constant

The libpq connection is in pipeline mode and an error occurred while processing the current pipeline. The aborted flag is cleared when PQgetResult returns a result of type PGRES_PIPELINE_SYNC.

Connection#pipeline_status constant

The libpq connection is not in pipeline mode.

Connection#pipeline_status constant

The libpq connection is in pipeline mode.

Flag for Connection#lo_lseek – seek from current position

Flag for Connection#lo_lseek – seek from object end

Flag for Connection#lo_lseek – seek from object start