Postgres Studio v0.3.0

An MCP server for your AI tools, psql in the console, and Settings in one place.

• MCP server (opt-in). Let Claude Code, Cursor, Codex or VS Code work with your saved connections. It runs only while the app is open, on 127.0.0.1 at a port you choose (47432 by default), behind a token kept in your system's keychain. You decide what clients may do: browsing, reading, writing rows, schema changes, any SQL, and seeing, editing or deleting connections are each Off, Ask or Allow, and each connection is closed, readable, or readable and writable. A request set to Ask brings the app to the front with an approval card showing the SQL; a write first runs as a dry run that counts the rows it would change and is rolled back. Reads run in a read-only transaction. "Add to Claude Code / Cursor / Codex / VS Code" writes the entry into that client's config file and keeps a .bak copy. Clients never see passwords or full connection strings, and a connection a client creates is saved without a password.
• psql in the console. Run a console through psql instead, per console or by default, for its meta-commands (\d, \copy, \i, \gexec, \if…) and your ~/.psqlrc. The app uses the psql already on your computer (PATH, Homebrew's libpq, Postgres.app, PostgreSQL's install folders, or one you pick) and never downloads one. The password reaches psql through its environment, never its command line. Results land in the same grid, psql's output streams into Messages, and Cancel or a time limit stops the run.
• Settings. One dialog, from the gear in the toolbar, Ctrl/Cmd+, or the palette: the theme (now also "system"), the rows a table tab and a console fetch, the console engine and psql options, import and export, the Assistant and the MCP server.
• Export and import. Pick the connections an export takes, or export a folder from its menu in the Explorer; folders travel with the connections. Import into the folder you choose; pgAdmin's groups become subfolders.
• Pick up where you left off. The last session's tabs come back on launch, with their queries and SQL, and connect only when you open them. Turn it off in Settings › General.

Also: pg_dump, pg_restore and psql are found on your login shell's PATH and in Homebrew's libpq, so an app started from the dock finds them too.

Postgres Studio v0.2.0

Native TimescaleDB support. It only shows up in databases with the extension installed; a database without it works as before.

• Hypertables are marked in the explorer and show their real size and row count, not the empty parent's. Their Structure adds the dimensions and chunk interval, the columnstore settings and compression totals, a chart of each chunk's size, the chunks (convert one to columnstore or back), and the policies with their jobs. Index sizes and scans come from the chunks.
• Continuous aggregates get a group of their own and show the query they were defined with, their bucket and source, how far they are materialized and their lag, and a real-time switch. Refresh any range of buckets, history included, from a dialog.
• Server activity has a Jobs view: every policy and job of your own, with its last run, failures and last error. Run a job now, or pause and resume it.
• Drop chunks older than an age, with a preview of what goes, the space freed and the continuous aggregates that read from the hypertable, and a typed confirmation.
• EXPLAIN names TimescaleDB's plan nodes (ChunkAppend, DeferredChunkAppend, ColumnarScan, VectorAgg…) and no longer loses DeferredChunkAppend's subtree. Completion knows TimescaleDB's functions, and the generated DDL recreates the hypertable, its columnstore and its policies.
• Restoring a backup that holds TimescaleDB runs between timescaledb_pre_restore() and timescaledb_post_restore(). ALTER EXTENSION timescaledb UPDATE runs in a session of its own, as the extension requires.
• Actions need TimescaleDB 2.18 or later, a connection that isn't read-only and, except dropping chunks, the Community edition. Every action shows its statement before it runs. On the Apache edition the app reads everything it can and says why the rest is missing.

Also fixed: the plan of an EXPLAIN run before any statement now shows up.

Postgres Studio v0.1.0

First release of Postgres Studio.

• Connections by URI or host/port, TLS up to verify-full, SSH tunnels, read-only connections, secrets in the OS keychain, pgAdmin servers.json import.
• Explorer of databases, schemas, objects, extensions and Apache AGE graphs; quick open across every schema.
• Table tabs with Data (typed grid, foreign keys both ways, pending edits committed in one transaction, CSV import), Structure (columns, constraints, indexes, triggers, DDL) and SQL views.
• SQL consoles with per-statement results, manual transactions, EXPLAIN plans, saved scripts, CSV/JSON export, and SQL files of any size run from disk.
• Backup and restore with pg_dump / pg_restore; server activity with cancel and terminate; roles; VACUUM / ANALYZE / REINDEX.
• Schema diagram with SVG export; Cypher (Apache AGE) and pgvector support.
• An opt-in Assistant that drives your own Claude Code or Codex CLI through read-only tools.