System Virtual Tables
System virtual tables in the system schema expose cluster runtime information and external-source metadata. They provide SQL-queryable alternatives to SHOW statements, with support for WHERE, ORDER BY, and LIMIT clauses.
System virtual tables filter rows by the caller’s privileges. Cluster runtime tables (system.nodes, system.queries, system.execs) are visible only to a superuser. Tables that expose catalog and connection metadata filter rows by the caller’s grants on the database, namespace (also called schema), and metadata.
|
Available tables
| Table | Equivalent statement | Description |
|---|---|---|
|
All catalogs (both Redpanda and Iceberg) visible to the caller. |
|
|
Iceberg catalogs with their REST endpoint, warehouse, and authentication type. |
|
|
Iceberg tables whose schema has been loaded into the local catalog. |
|
|
Redpanda catalog connections, including any linked Iceberg catalog. |
|
|
Tables mapped to Redpanda topics through a Redpanda catalog. |
|
|
Current state of all nodes in the cluster. |
|
|
Currently running queries. |
|
|
Currently running execution tasks. |
system.catalogs
All catalogs in the cluster (both Redpanda and Iceberg), across databases and schemas visible to the caller.
| Column | Type | Nullable | Description |
|---|---|---|---|
|
|
No |
Catalog name. |
|
|
No |
Schema containing the catalog. |
|
|
No |
Catalog type: |
SELECT * FROM system.catalogs;
For per-catalog detail, query system.iceberg_catalogs or system.kafka_connections.
system.iceberg_catalogs
Iceberg catalog connections, with their REST endpoint and authentication details.
| Column | Type | Nullable | Description |
|---|---|---|---|
|
|
No |
Iceberg catalog name. |
|
|
No |
REST catalog endpoint URI. |
|
|
No |
Iceberg warehouse identifier or location. |
|
|
No |
Authentication type for the REST catalog. One of |
|
|
No |
Schema containing the catalog. |
|
|
No |
Database containing the catalog. |
SELECT name, uri, auth_type FROM system.iceberg_catalogs;
system.iceberg_tables
Iceberg tables whose schema has been loaded into the local catalog. Schemas are loaded by an explicit REFRESH statement or auto-loaded when you CREATE TABLE against an Iceberg catalog. See Query Iceberg-enabled Topics for details on when to refresh. Each row represents one root Iceberg table.
| Column | Type | Nullable | Description |
|---|---|---|---|
|
|
No |
Database containing the registered table. |
|
|
No |
Schema containing the registered table. |
|
|
No |
Iceberg catalog the table belongs to. |
|
|
No |
Qualified Iceberg table path (for example, |
|
|
No |
Object identifier of the table type. Joinable with |
|
Stale entries: dropping an Iceberg table from the REST catalog leaves its registration in the Redpanda SQL catalog until you drop it explicitly. The view continues to list it. This mirrors |
SELECT * FROM system.iceberg_tables WHERE catalog_name = 'lakehouse_catalog';
system.kafka_connections
Redpanda catalog connections, including any linked Iceberg catalog for queries that span live records and Iceberg-translated history. For details on linking and Iceberg-translated history, see ALTER REDPANDA CATALOG.
| Column | Type | Nullable | Description |
|---|---|---|---|
|
|
No |
Database containing the connection. |
|
|
No |
Schema containing the connection. |
|
|
No |
Catalog (connection) name. |
|
|
No |
Connection options as a comma-separated string of |
|
|
Yes |
Linked Iceberg catalog as |
SELECT name, iceberg_catalog FROM system.kafka_connections;
system.kafka_sources
Tables mapped to Redpanda topics through a Redpanda catalog. One row per CREATE TABLE catalog⇒name WITH (…) mapping.
| Column | Type | Nullable | Description |
|---|---|---|---|
|
|
No |
Database containing the source table. |
|
|
No |
Schema containing the source table. |
|
|
No |
Table name. |
|
|
No |
Redpanda catalog (connection) the table belongs to. |
|
|
No |
Source topic name. |
|
|
No |
Schema Registry subject name. Empty if not configured. |
|
|
No |
Schema lookup policy. See CREATE TABLE. |
|
|
No |
Deserialization error-handling policy. See CREATE TABLE. |
|
|
No |
Nested-struct mapping policy. See CREATE TABLE. |
|
|
No |
Full Protobuf message name. Empty if not configured. |
SELECT name, topic_name, subject_name FROM system.kafka_sources
WHERE connection_name = 'production_redpanda';
system.nodes
Current state of each node in the cluster. Visible only to a superuser. For the column reference, see SHOW NODES.
SELECT * FROM system.nodes;
system.queries
Currently running queries on the cluster. Visible only to a superuser.
| Column | Type | Nullable | Description |
|---|---|---|---|
|
|
No |
Query identifier. |
|
|
No |
Identifier of the node that received the query from the client. |
|
|
No |
Identifier of the node scheduling the query’s execution tasks. |
|
|
No |
Number of worker tasks assigned to the query. |
|
|
No |
Current state of the query. |
|
|
No |
Time the query was received. |
|
|
Yes |
Time the query was accepted for execution. |
|
|
Yes |
Time the query’s execution tasks were scheduled. |
|
|
Yes |
Time execution started. |
|
|
Yes |
Time execution finished. |
SELECT qid, state, created FROM system.queries WHERE state <> 'FINISHED';
system.execs
Currently running execution tasks across the cluster. Visible only to a superuser. Each query in system.queries typically corresponds to one or more rows in this table.
| Column | Type | Nullable | Description |
|---|---|---|---|
|
|
No |
Node executing the task. |
|
|
No |
Identifier of the parent query. Join with |
|
|
Yes |
Identifier of the data task within the query. |
|
|
No |
Current state of the execution task. |
|
|
No |
Memory consumed by the task, in bytes. |
|
|
No |
|
SELECT node, qid, state, memory FROM system.execs ORDER BY memory DESC;