REJECTED_TIMESTAMP

TIMESTAMPTZ

Time when Vertica rejected the resource.

NODE_NAME

VARCHAR

Name of the node that is reporting the requested information.

USER_NAME

VARCHAR

Name of the user at the time Vertica recorded the session.

SESSION_ID

VARCHAR

Identifier for this session. This identifier is unique within the cluster at any point in time but can be reused when the session closes.

REQUEST_ID

INTEGER

Unique identifier of the query request in the user session.

TRANSACTION_ID

INTEGER

Identifier for the transaction within the session, if any; otherwise NULL.

STATEMENT_ID

INTEGER

Unique numeric ID for the currently-running statement. NULL indicates that no statement is currently being processed. The combination of TRANSACTION_ID, STATEMENT_ID, and REQUEST_ID uniquely identifies a statement within a session.

POOL_ID

INTEGER

Catalog-assigned integer value that uniquely identifies the resource pool.

POOL_NAME

VARCHAR

Name of the resource pool

REASON

VARCHAR

Reason for rejecting this request; for example:

• Usage of single request exceeds high limit
• Timed out waiting for resource reservation
• Canceled waiting for resource reservation

RESOURCE_TYPE

VARCHAR

Memory, threads, file handles or execution slots.

The following list shows the resources that are limited by the resource manager. A query might need some amount of each resource, and if the amount needed is not available, the query is queued and could eventually time out of the queue and be rejected.

• Number of running plans
• Number of running plans on initiator node (local)
• Number of requested threads
• Number of requested file handles
• Number of requested KB of memory
• Number of requested KB of address space

Note: Execution slots are determined by MAXCONCURRENCY parameter.

REJECTED_VALUE

INTEGER

Amount of the specific resource requested by the last rejection