Nearly all of the feature claims below come from the vendor and from Laravel News coverage. I haven't tested the tool, and nobody has independently audited its privacy or safety claims.
What happened
PostgreSQL's project news page lists pgjumbo as a new desktop client, free to use, for Windows, macOS and Linux, with query, data and administration tools. The announcement went out on 18 November 2026. Laravel News followed on 20 November.
The version numbers have been moving fast, so don't trust any one of them:
- The PostgreSQL announcement describes version 1.0.2.
- Search results for the vendor's download page showed 1.0.4.
- The download page we inspected showed 1.0.5, released 20 November 2026.
Treat 1.0.2 as the version in the announcement and 1.0.5 as the newest build we saw.
The headline feature: preview before you write
Most database GUIs run your UPDATE or DELETE and let you find out afterwards. pgjumbo tries to flip that order.
- Estimate first. Put the cursor in an UPDATE or a DELETE and pgjumbo counts the rows, names the triggers and cascades, and offers Rehearse. The row count is the planner's estimate, so nothing runs to produce it.
- Count exactly. If the estimate isn't good enough, this button runs a read-only
count(*)built from the statement'sWHEREclause, for up to 10 seconds. - Rehearse. It runs an
UPDATE,DELETEorMERGEinside an uncommitted transaction. It lists every row changed, with old and new values side by side. The vendor says Commit keeps the change and supplies a script to undo it, while Roll Back leaves the tables as they were. - Savepoints. Each statement gets its own savepoint, so a typo undoes only that statement and leaves earlier ones in place.
- Commit modes. There are three: Auto-commit, Smart commit and Manual commit. Smart commit opens a transaction only at your first write, so a read-only session never holds one open.
Two caveats apply. A planner estimate is only an estimate, which is why the exact-count option exists. And Rehearse can be committed, so it isn't a promise that nothing changes. It is a way to look before you decide.
Plans and "What if"
The Explain tab draws the plan as a diagram, ties each step to the SQL it came from, and marks the slowest step. "What if" compares your current plan with the plan you'd get from an index that doesn't exist yet, or from a different planner setting such as work_mem. Both plans come from a plain EXPLAIN in that tab's session, so no index is built and other connections are unaffected.
This is a plan comparison, not a benchmark. A plan that looks cheaper doesn't guarantee a real index will perform the same once it exists and your data changes.
The vendor's homepage also advertises per-statement plan history on production and a profiler that shows line-by-line time inside called PL/pgSQL functions. I haven't verified either.
The optional Claude Code assistant
The Assistant is the part that will draw the most questions from security-minded teams.
- It's off by default. The vendor says nothing is sent anywhere when it's off.
- It runs the Claude Code installation already on your machine, signed in to your own Claude plan or API key. pgjumbo has no Claude account of its own.
- You set what it may read for each server type. The vendor's starting defaults, from its homepage:
| Read | Dev | Staging | Production |
|---|---|---|---|
| Structure | Allow | Allow | Allow |
| Statistics | Allow | Allow | Allow |
| Query text | Allow | Allow | Ask |
| Row data | Ask | Ask | Every time |
| Repositories | Allow | Allow | Ask |
- SQL it suggests is checked by PostgreSQL's own parser, and nothing runs until you run it.
These are product-stated defaults. If you handle regulated data, review them before enabling the Assistant, especially for "Allow" on query text, since queries can contain literal values.
Windows install notes
For a Windows audience, the download page is the most useful part.
- Supported systems: Windows 10 or 11, on x64 or ARM64. The page says to check Settings, then System, then About, and read the System type line to pick the right file.
- Per-user installer (.exe): it installs for your user and needs no administrator rights. It shows the licence first, and you choose I Agree.
- MSI package: the page recommends it for installing for every user or through a management tool. This is the one for Intune or SCCM-style deployments.
- SmartScreen: the page says pgjumbo is not code-signed yet, so Windows SmartScreen may warn about an unrecognised app. You click More info, then Run anyway. Admins may want to check hashes and allow-list the package before rolling it out, rather than training users to click through warnings.
- WebView2: on Windows 10, the installer downloads and adds Microsoft's WebView2 runtime if it's missing. Windows 11 already includes it.
- Hash check: the page publishes SHA-256 values and shows the PowerShell command
Get-FileHashfor verifying a download. It also signs the checksums with a PGP key. - winget: a pull request in Microsoft's winget-pkgs repository, opened by the developer, describes four installers: a per-user NSIS installer and a machine-wide MSI, each for x64 and arm64. I saw only the pull request. I can't confirm it has been merged or that the package is installable.
- Backup tools: backup and restore need PostgreSQL's client programs (
pg_dump,pg_dumpall,pg_restore,psql) installed. The page sayspg_dumpmust be at least as new as the server it backs up.
Server support and connections
The vendor's homepage says it connects to PostgreSQL 14 to 19, with 12 and 13 as best effort, plus Amazon RDS and Aurora with IAM sign-in, and servers behind SSH, in every TLS mode. The PostgreSQL announcement simplifies this to "12+". Use the product's more qualified wording if exact support matters to you.
The 1.0.2 release notes mention restoring into a new database on server versions 12 to 18. That describes one restore feature, not a lack of PostgreSQL 19 support.
The rest of the toolbox
The announcement lists a broad feature set:
- an object explorer and inspector
- a Query Tool with parser-based syntax errors
- a data editor that previews statements before saving
- backup, restore and maintenance workflows
- server activity, roles and privileges, logs, replication,
pg_cronjobs andLISTEN/NOTIFY
Object changes are shown as SQL for review. On servers marked Production, destructive statements ask for confirmation first.
Version 1.0.2 rebuilt backup, restore and maintenance:
- You can pick tables with or without rows.
- Whole-server backups become a folder of per-database archives.
- You can preview an archive before restoring it.
- Tasks run in the background with progress.
- Per-table autovacuum settings are exposed.
COPYto a program or server file on Production now asks first.
How it compares
A third-party writeup by Byteiota calls it a direct upgrade for people tolerating pgAdmin, and says it fills much of the gap for people eyeing TablePlus. That is opinion from a single site, not a benchmark. The tool is days old and at 1.0.x, so expect rough edges. It is also not code-signed on Windows yet. For production work, try it first against a staging database and check what its previews say against what actually happens.
Bottom line
- pgjumbo is a free PostgreSQL client for Windows 10/11 (x64 and ARM64), macOS and Linux.
- Its focus is previewing writes: planner-based estimates, an exact-count option, a rehearsal that can be committed or rolled back, and per-statement savepoints.
- The Claude-based Assistant is optional and off by default. Its read permissions are set per server type.
- Windows admins get MSI packages and published checksums. They also get an unsigned-app SmartScreen warning and a WebView2 dependency on Windows 10.
- Nearly everything here is vendor-stated, so test it before relying on it.
References
- pgjumbo: A PostgreSQL Client for macOS, Windows, and Linux Laravel News · 2026-11-20T14:00:00+00:00
- PostgreSQL: pgjumbo: a new free desktop client for PostgreSQL postgresql.org
- Download a free PostgreSQL client pgjumbo.com