CURRENT_SCHEMA

Return the name of the schema (namespace) bound to the current session.

Syntax

CURRENT_SCHEMA()

Description

## Overview Returns the name of the current schema for the session. The schema is the middle level in the three-part name hierarchy (catalog.schema.table). Use this function to build fully qualified identifiers, to scope information_schema queries, or to include context in audit output. ## Session context - The value is the schema the session is currently using, as set at connection time or by `SET SCHEMA` / `USE SCHEMA`. - Takes no arguments; both `CURRENT_SCHEMA` and `CURRENT_SCHEMA()` are accepted. - Never returns NULL. ## Behavior - Always returns a non-NULL string. - Deterministic for the duration of the current binding. - Side effect free. ## Compatibility - Matches the SQL-standard CURRENT_SCHEMA.

Examples

-- Read the active schema
SELECT CURRENT_SCHEMA();

-- Build a fully qualified table reference
SELECT CURRENT_CATALOG() || '.' || CURRENT_SCHEMA() || '.events' AS fqn;

-- Session diagnostics snapshot
SELECT CURRENT_DATABASE() AS db, CURRENT_SCHEMA() AS schema_name, CURRENT_USER() AS user_name;

-- Limit information_schema browsing to the active schema
SELECT table_name FROM information_schema.tables
WHERE table_schema = CURRENT_SCHEMA();

Pitfalls

• CURRENT_SCHEMA reflects the session binding, not the schema referenced in a specific query. A query that names `other_schema.table` reads from `other_schema` even though CURRENT_SCHEMA returns the default.
• Switching schemas mid-session changes the return value. Stamp audit rows with CURRENT_SCHEMA at write time rather than at reporting time.
• Some engines return a search path (a list of schemas) rather than a single name for CURRENT_SCHEMA. DeltaForge returns a single schema name; consult PG-compat docs if you are porting from an engine with a search path.
• Case sensitivity follows the declared schema name. Do not assume lowercase comparison.

See Also

• current_catalog
• current_database
• current_user