Resource Types
Examples
PostgreSQL
PHP Manual

# Predefined Constants

The constants below are defined by this extension, and will only be available when the extension has either been compiled into PHP or dynamically loaded at runtime.

`PGSQL_LIBPQ_VERSION` (string)
  Short libpq version that contains only numbers and dots.
`PGSQL_LIBPQ_VERSION_STR` (string)
  Long libpq version that includes compiler information.
`PGSQL_ASSOC` (integer)
  Passed to pg_fetch_array(). Return an associative array of field names and values.
`PGSQL_NUM` (integer)
  Passed to pg_fetch_array(). Return a numerically indexed array of field numbers and values.
`PGSQL_BOTH` (integer)
  Passed to pg_fetch_array(). Return an array of field values that is both numerically indexed (by field number) and associated (by field name).
`PGSQL_CONNECT_FORCE_NEW` (integer)
  Passed to pg_connect() to force the creation of a new connection, rather than re-using an existing identical connection.
`PGSQL_CONNECT_ASYNC` (integer)
  Passed to pg_connect() to create an asynchronous connection. Added in PHP 5.6.0.
`PGSQL_CONNECTION_BAD` (integer)
  Returned by pg_connection_status() indicating that the database connection is in an invalid state.
`PGSQL_CONNECTION_OK` (integer)
  Returned by pg_connection_status() indicating that the database connection is in a valid state.
`PGSQL_SEEK_SET` (integer)
  Passed to pg_lo_seek(). Seek operation is to begin from the start of the object.
`PGSQL_SEEK_CUR` (integer)
  Passed to pg_lo_seek(). Seek operation is to begin from the current position.
`PGSQL_SEEK_END` (integer)
  Passed to pg_lo_seek(). Seek operation is to begin from the end of the object.
`PGSQL_EMPTY_QUERY` (integer)
  Returned by pg_result_status(). The string sent to the server was empty.
`PGSQL_COMMAND_OK` (integer)
  Returned by pg_result_status(). Successful completion of a command returning no data.
`PGSQL_TUPLES_OK` (integer)
  Returned by pg_result_status(). Successful completion of a command returning data (such as a SELECT or SHOW).
`PGSQL_COPY_OUT` (integer)
  Returned by pg_result_status(). Copy Out (from server) data transfer started.
`PGSQL_COPY_IN` (integer)
  Returned by pg_result_status(). Copy In (to server) data transfer started.
`PGSQL_BAD_RESPONSE` (integer)
  Returned by pg_result_status(). The server's response was not understood.
`PGSQL_NONFATAL_ERROR` (integer)
  Returned by pg_result_status(). A nonfatal error (a notice or warning) occurred.
`PGSQL_FATAL_ERROR` (integer)
  Returned by pg_result_status(). A fatal error occurred.
`PGSQL_TRANSACTION_IDLE` (integer)
  Returned by pg_transaction_status(). Connection is currently idle, not in a transaction.
`PGSQL_TRANSACTION_ACTIVE` (integer)
  Returned by pg_transaction_status(). A command is in progress on the connection. A query has been sent via the connection and not yet completed.
`PGSQL_TRANSACTION_INTRANS` (integer)
  Returned by pg_transaction_status(). The connection is idle, in a transaction block.
`PGSQL_TRANSACTION_INERROR` (integer)
  Returned by pg_transaction_status(). The connection is idle, in a failed transaction block.
`PGSQL_TRANSACTION_UNKNOWN` (integer)
  Returned by pg_transaction_status(). The connection is bad.
`PGSQL_DIAG_SEVERITY` (integer)
  Passed to pg_result_error_field(). 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.
`PGSQL_DIAG_SQLSTATE` (integer)
  Passed to pg_result_error_field(). 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. This field is not localizable, and is always present.
`PGSQL_DIAG_MESSAGE_PRIMARY` (integer)
  Passed to pg_result_error_field(). The primary human-readable error message (typically one line). Always present.
`PGSQL_DIAG_MESSAGE_DETAIL` (integer)
  Passed to pg_result_error_field(). Detail: an optional secondary error message carrying more detail about the problem. May run to multiple lines.
`PGSQL_DIAG_MESSAGE_HINT` (integer)
  Passed to pg_result_error_field(). 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. May run to multiple lines.
`PGSQL_DIAG_STATEMENT_POSITION` (integer)
  Passed to pg_result_error_field(). 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.
`PGSQL_DIAG_INTERNAL_POSITION` (integer)
  Passed to pg_result_error_field(). 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.
`PGSQL_DIAG_INTERNAL_QUERY` (integer)
  Passed to pg_result_error_field(). The text of a failed internally-generated command. This could be, for example, a SQL query issued by a PL/pgSQL function.
`PGSQL_DIAG_CONTEXT` (integer)
  Passed to pg_result_error_field(). 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.
`PGSQL_DIAG_SOURCE_FILE` (integer)
  Passed to pg_result_error_field(). The file name of the PostgreSQL source-code location where the error was reported.
`PGSQL_DIAG_SOURCE_LINE` (integer)
  Passed to pg_result_error_field(). The line number of the PostgreSQL source-code location where the error was reported.
`PGSQL_DIAG_SOURCE_FUNCTION` (integer)
  Passed to pg_result_error_field(). The name of the PostgreSQL source-code function reporting the error.
`PGSQL_ERRORS_TERSE` (integer)
  Passed to pg_set_error_verbosity(). Specified that returned messages include severity, primary text, and position only; this will normally fit on a single line.
`PGSQL_ERRORS_DEFAULT` (integer)
  Passed to pg_set_error_verbosity(). The default mode produces messages that include the above plus any detail, hint, or context fields (these may span multiple lines).
`PGSQL_ERRORS_VERBOSE` (integer)
  Passed to pg_set_error_verbosity(). The verbose mode includes all available fields.
`PGSQL_STATUS_LONG` (integer)
  Passed to pg_result_status(). Indicates that numerical result code is desired.
`PGSQL_STATUS_STRING` (integer)
  Passed to pg_result_status(). Indicates that textual result command tag is desired.
`PGSQL_CONV_IGNORE_DEFAULT` (integer)
  Passed to pg_convert(). Ignore default values in the table during conversion.
`PGSQL_CONV_FORCE_NULL` (integer)
  Passed to pg_convert(). Use SQL NULL in place of an empty string.
`PGSQL_CONV_IGNORE_NOT_NULL` (integer)
  Passed to pg_convert(). Ignore conversion of `NULL` into SQL NOT NULL columns.
`PGSQL_DML_NO_CONV` (integer)
  Passed to pg_insert(), pg_select(), pg_update() and pg_delete(). All parameters passed as is. Manual escape is required if parameters contain user supplied data. Use pg_escape_string() for it.
`PGSQL_DML_EXEC` (integer)
  Passed to pg_insert(), pg_select(), pg_update() and pg_delete(). Execute query by these functions.
`PGSQL_DML_ASYNC` (integer)
  Passed to pg_insert(), pg_select(), pg_update() and pg_delete(). Execute asynchronous query by these functions.
`PGSQL_DML_STRING` (integer)
  Passed to pg_insert(), pg_select(), pg_update() and pg_delete(). Return executed query string.
`PGSQL_DML_ESCAPE` (integer)
  Passed to pg_insert(), pg_select(), pg_update() and pg_delete(). Apply escape to all parameters instead of calling pg_convert() internally. This option omits meta data look up. Query could be as fast as pg_query() and pg_send_query().
`PGSQL_POLLING_FAILED` (integer)
  Returned by pg_connect_poll() to indicate that the connection attempt failed.
`PGSQL_POLLING_READING` (integer)
  Returned by pg_connect_poll() to indicate that the connection is waiting for the PostgreSQL socket to be readable.
`PGSQL_POLLING_WRITING` (integer)
  Returned by pg_connect_poll() to indicate that the connection is waiting for the PostgreSQL socket to be writable.
`PGSQL_POLLING_OK` (integer)
  Returned by pg_connect_poll() to indicate that the connection is ready to be used.
`PGSQL_POLLING_ACTIVE` (integer)
  Returned by pg_connect_poll() to indicate that the connection is currently active.

Resource Types
Examples
PostgreSQL
PHP Manual