

Sections under a PostgreSQL schema, with one overloaded function open
Engine support
A section appears only when the schema holds at least one object of that kind, so a database with no tables still lists its procedures and functions, and one with no triggers shows no Triggers section. A schema that holds nothing shows No items, or Loading… while its lists are on their way. A list the server refused keeps its section and shows the error in place of its rows.
Events and extensions
The engines in this table list one more kind of object in each database:
With View > Sidebar as List both are sections after the others. The same rules apply as to the rest: a section shows only when it has a row, and a list the server refused shows its error. Point at a row for an event’s schedule, status and definer, or an extension’s version, schema and owner.
Both are read-only here. Return, a double-click or Show DDL opens the definition in the same viewer as a routine’s source, and Copy Name is on the menu. An event opens as the server’s
CREATE EVENT, an extension as CREATE EXTENSION IF NOT EXISTS … WITH SCHEMA … with its comment. To enable, disable, create or drop one, run ALTER EVENT, CREATE EXTENSION or DROP … in a query tab.
Finding a routine or trigger
A trigger row carries the table it fires for beside its name. The sidebar filter matches a trigger by its own name or by that table; type-select matches the name only. Triggers also appear on their table’s Structure tab. File > Open Quickly… (Cmd+Shift+O) indexes all three kinds alongside tables and views. Choosing one opens its source.
Overloaded names
PostgreSQL lets several functions share a name with different argument lists. Where a name repeats inside a section, every row in that group gains its arguments:transform(geometry, integer) and transform(geometry, text). A unique name stays bare. Each row opens its own definition.
Reading the source
Return or a double-click opens the selected row. Right-click offers Show DDL for the same thing, plus Copy Name and Copy with Signature. With the Routine Debugger turned on, a PL/pgSQL or PL/SQL routine also offers Debug….
Beside the source sit the properties the engine reports: language, return type, volatility, security, and owner for a routine; timing, events, orientation, and enabled state for a trigger. The labels are the engine’s own, so they differ between engines.
A viewer tab survives a relaunch and refetches when it reopens.
A DuckDB macro shows the expression DuckDB stored, not the
CREATE MACRO text as typed.
