Vertica Analytics Platform Version 10.1.x Documentation

LOCKS

Monitors lock grants and requests for all nodes. A table call with no results indicates that no locks are in use.

Column Name Data Type Description
NODE_NAMES

VARCHAR

Nodes on which lock interaction occurs.

Node Rollup:

NODE_NAMES are separated by commas. A transaction can have the same lock in the same mode in the same scope on multiple nodes. However, the transaction gets only one (1) line in the table.

OBJECT_NAME

VARCHAR

Name of object being locked; can be a table or an internal structure (projection, global catalog, or local catalog).

OBJECT_ID

INTEGER

Unique numeric ID assigned by the Vertica catalog that identifies the object being locked.

TRANSACTION_ID

VARCHAR

Identification of transaction within the session, if any; otherwise NULL. Useful for creating joins to other system tables.

TRANSACTION_DESCRIPTION

VARCHAR

Identification of transaction and associated description. Typically this query caused the transaction's creation.

LOCK_MODE

VARCHAR

Intended operation of the transaction. For a list of lock modes and compatibility, see Lock Modes

LOCK_SCOPE

VARCHAR

Expected duration of the lock after it is granted. Before the lock is granted, Vertica lists the scope as REQUESTED.

Once a lock has been granted, the following scopes are possible:

  • STATEMENT_LOCALPLAN
  • STATEMENT_COMPILE
  • STATEMENT_EXECUTE
  • TRANSACTION_POSTCOMMIT
  • TRANSACTION

All scopes, other than TRANSACTION, are transient and are used only as part of normal query processing.

REQUEST_TIMESTAMP 

TIMESTAMP

Time when the transaction began waiting on the lock.

GRANT_TIMESTAMP

TIMESTAMP

Time the transaction acquired or upgraded the lock:

  • Return values are NULL until the grant occurs.
  • If the grant occurs immediately, values might be the same as REQUEST_TIMESTAMP.