INTERRUPT_STATEMENT

INTERRUPT_STATEMENT interrupts the specified statement (within an external session), rolls back the current transaction, and writes a success or failure message to the log file.

Syntax

INTERRUPT_STATEMENT(sessionid, stmtid)

Semantics

sessionid	specifies the session to interrupt. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
stmtid	specifies the statement to interrupt

Notes

Only statements being run by external sessions can be interrupted.
Sessions may be interrupted while idle or during statement execution.
If the stmtid is valid, the statement is interruptible, and the command is successfully sent, the command returns a success message. Otherwise it returns an error.

Messages

Are these written to vertica.log and/or returned to the vsql console or SQLSTATE?

Statement interrupt sent. Check VT_SESSIONS for progress.

Success.

Session <id> could not be successfully interrupted: session not found

The session ID argument to the interrupt command does not match a running session.

Session <id> could not be successfully interrupted: statement not found

The statement ID does not (or no longer) matches the ID of a running statement (if any).

The running statement cannot be interrupted.

If the statement is DDL or otherwise non-interruptible.

What non-DDL statements are non-interruptible?

Internal (system) sessions cannot be interrupted.

The session is internal.

Examples