Documentation / Workbench Cockpit

Workbench Cockpit

The Cockpit is a structural view. It uses the active DatabaseContext and the current Code Moniker index; it never displays table rows.

Cockpit map

Each numbered marker corresponds to an explanation below the image.

1 2 3 4 5 6

1. Sources tree. Browse schemas and indexed objects lazily. Expanding an object shows direct incoming and outgoing relations known by the index.
2. Scope and search. Search by object name, #schema, or @type. Upstream and downstream controls set graph exploration depth, not zoom.
3. Relation filters. Show or hide calls, reads, writes, references, and type usages without changing the underlying index.
4. Focused graph. The selected object anchors the view. Expand neighbors in place, drag nodes to preserve a mental map, and recenter without recomputing the graph.
5. Source inspector. Read the indexed PostgreSQL definition for the selected object. Hidden neighbors disclose relations omitted by current depth and ranking limits.
6. Pins and perspectives. Pin objects across navigation and save a perspective to restore scope, filters, selected object, positions, and expansion settings.

Where the relations come from

The Cockpit and Sources tree use the same indexed relations. They show direct calls, reads, writes, references, and type usages from the PostgreSQL definitions currently indexed for the active database.

Automatic DDL synchronization

Schema synchronization is opt-in. PostgreSQL event triggers publish committed structural changes to a dedicated listener. Identifiable objects and their direct indexed dependants are reprojected incrementally. Ambiguous drops, broad schema changes, missed events, or failed incremental updates make the index stale and require a complete refresh.

Enable postgresql-workbench.workbench.schemaSync.enabled, then run Provision Schema Synchronization explicitly. PostgreSQL superuser privileges are required to create database event triggers.

A fresh index means structural definitions are synchronized. It does not mean table data was read or monitored. INSERT, UPDATE, and DELETE never trigger Workbench index synchronization.