Catalog
Object counts and quick links into the catalog.
Before a schema review, opens Database overview to see object counts at a glance — 47 tables, 12 views, 3 extensions — and clicks through to trouble spots.
The Catalog panel Overview 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 Overview from the left sidebar after you connect; everything here reflects the live connection, not a cached export from yesterday.
Bridge path: /database/overview

Step 1
Overview shows scale: hundreds of indexes might mean migration risk; zero extensions might mean missing pgvector.
Each count links deeper into catalog.
Object counts and quick links into the catalog. Path /database/overview. Summarizes tables, views, indexes, extensions for active connection.

Step 2
New hire connects read-only staging, reads overview, knows where to start — Tables before Triggers.
Faster than a wiki that rotted in Confluence.
Landing panel in Catalog section. Pairs with Schema map for visual learners.

Step 3
Pulse looks odd — overview confirms extension count jumped after deploy. Rollback decision in minutes.
Overview is the table of contents for the database story.
Cross-link to Workspace → Pulse and Ops panels when counts shift unexpectedly.

postgresql://, ssh://, sftp://, s3://, or smtp:// examples.Related connections