Catalog

Indexes

Name: Nexoxa Bridge
Author: Nexoxa

B-tree, GIN, GiST, and vector indexes with stats.

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.

EXPLAIN shows seq scan, opens Indexes — B-tree, GIN, GiST, vector indexes with stats — and prototypes missing index in Query lab.

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

Bridge path: /database/indexes

Step 1

Every index with type

orders_created_at_idx exists but unused — candidate to drop. New GIN on jsonb column missing — candidate to add.
Stats beside names.

B-tree, GIN, GiST, and vector indexes with stats. /database/indexes. Index types and usage where available.

Step 2

Indexing studio mindset

Compare duplicate indexes on same column set — drop one, deploy, watch Pulse.
Iterative tuning loop.

EXPLAIN in Query lab validates changes.

Step 3

Vector indexes

pgvector HNSW listed next to btree — embedding search tuning starts in catalog.
Link to Vectors panel.

Pair with Catalog → Vectors for column-level detail.

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