Catalog

Materialized views

Name: Nexoxa Bridge
Author: Nexoxa

Refresh state and storage on materialized views.

The story

These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.

Dashboard slow after lunch, opens Mat. views — reporting.daily_revenue shows stale refresh — and schedules REFRESH before exec demo.

The Catalog panel Mat. views is where Bridge turns raw metadata into decisions — counts, definitions, dependencies, and links into the grid or Query lab. No information_schema archaeology; no guessing which mat view is stale.

Open Mat. views from the left sidebar after you connect; everything here reflects the live connection, not a cached export from yesterday.

Bridge path: /database/materialized-views

Step 1

Refresh state and storage

Stale badge on daily_revenue — last refresh 18 hours ago. One click to refresh command.
Storage size shows mat view worth keeping.

Refresh state and storage on materialized views. /database/materialized-views. Refresh timestamps and size.

Step 2

Open refresh commands

CONCURRENTLY option copied to Query lab — run off-peak.
Demo saved.

Refresh SQL templates per engine capabilities.

Step 3

When to mat view

Team debates new mat view — check existing mat views panel for overlap.
Avoid duplicate aggregates.

Pair with Views for dependency graph.

This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for postgresql://, ssh://, sftp://, s3://, or smtp:// examples.

Related connections

Database connection URLs