Catalog

Extensions catalog

Name: Nexoxa Bridge
Author: Nexoxa

Installed Postgres extensions and versions.

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.

PostGIS missing on staging, opens Extensions — installed names and versions — enables from UI or copies CREATE EXTENSION.

The Catalog panel Extensions 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 Extensions from the left sidebar after you connect; everything here reflects the live connection, not a cached export from yesterday.

Bridge path: /database/extensions

Step 1

Installed extensions

pgvector 0.7.0 on prod, missing on staging — parity fix before feature branch merge.
Version column guides upgrade.

Installed Postgres extensions and versions. /database/extensions. Installed extension catalog.

Step 2

Enable PostGIS, citext, pgvector

Enable flow or SQL snippet — run on staging, verify in overview counts.
Feature unblocked.

UI enable where supported; SQL fallback in lab.

Step 3

Extension dependents

Vectors panel empty until pgvector enabled — extensions first.
Order of operations clear.

Cross-panel dependencies documented in workflow.

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