Try PostgreSQL 19 SQL from a Desktop GUI (REPACK, ON CONFLICT DO SELECT, Visual EXPLAIN)
Try PostgreSQL 19 SQL from a desktop GUI: run REPACK and INSERT ... ON CONFLICT DO SELECT in HiDataLinker, use COPY TO FORMAT json on the server, and inspect plans with visual EXPLAIN ANALYZE / BUFFERS.
PostgreSQL 19 is scheduled for general availability on 19 November 2026. The project published PostgreSQL 19 RC 2 on 12 November 2026. As of this morning (Asia/Shanghai), the official news archive has not yet posted a 19.0 announcement, and the release notes still show a placeholder date. The 19 docs already describe the new SQL. This guide shows how to try it from HiDataLinker, a free MIT PostgreSQL desktop GUI (MySQL in the same client): local-first credentials, URL paste, Dump / same-engine migrate, and no seat or connection or tab freemium wall.
These statements are valid only on PostgreSQL 19+. Confirm the server with SELECT version();. Use a 19 RC 2 instance, or 19.0 once the project announces it.
What HiDataLinker actually ships
HiDataLinker v1.3.0 includes a SQL editor and visual EXPLAIN with optional ANALYZE and BUFFERS. You can paste a postgresql:// URL (or a DATABASE_URL), keep the profile on your machine, and run the documented PostgreSQL 19 statements yourself.
It does not ship a REPACK wizard or a COPY FORMAT json export button. It also does not provide PostgreSQL 19 property-graph support: official Beta 4 (24 September 2026) withdrew SQL/PGQ, so property graphs are not a current PostgreSQL 19 feature.
1. Connect to a PostgreSQL 19 server
- Install from hidatalinker.onesolo.app.
- Open New Connection — paste the URI or fill host, port, user, password, and database. See paste a DATABASE_URL.
- Test, then connect. Profiles stay on your machine — local-first, no hosted workspace.
- Optionally switch database on the same connection (v1.3.0) without creating another profile.
On a managed host, finish allowlists and TLS in the provider console first. HiDataLinker is the desktop client, not the cloud console.
2. Run REPACK in the SQL editor (not a wizard)
Per the official REPACK docs, REPACK rewrites a table to reclaim space occupied by dead tuples. Unlike VACUUM, it can return unused space to the operating system. REPACK (CONCURRENTLY) lets other transactions keep using the table; without CONCURRENTLY, the command takes an ACCESS EXCLUSIVE lock. You need the MAINTAIN privilege on the table.
REPACK (CONCURRENTLY, VERBOSE) my_table;
USING INDEX physically reorders rows (see the docs' notes on clustering). A database-wide REPACK with no table name cannot use CONCURRENTLY and cannot run inside a transaction block. Type the statement in HiDataLinker's SQL editor and run it — there is no in-app maintenance wizard.
3. INSERT ... ON CONFLICT DO SELECT (get or create)
INSERT in PostgreSQL 19 adds ON CONFLICT DO SELECT: an atomic insert-or-select, also called an idempotent insert or get or create. Official rules: you must provide a RETURNING clause and a conflict_target. DO SELECT needs SELECT privilege; DO SELECT FOR UPDATE/SHARE also needs UPDATE privilege.
INSERT INTO items (sku, name)
VALUES ('ABC-1', 'Widget')
ON CONFLICT (sku) DO SELECT
RETURNING *;
Run this in the SQL editor on PostgreSQL 19+. On older major versions the parser will reject DO SELECT.
4. COPY TO FORMAT json (export only)
COPY in PostgreSQL 19 adds FORMAT json. Officially, json is allowed only in COPY TO, not COPY FROM. A filename is interpreted on the database server, not your laptop.
COPY (SELECT sku, name FROM items)
TO '/tmp/items.json'
WITH (FORMAT json);
HiDataLinker does not ship a COPY FORMAT json export wizard. Do not expect COPY FROM ... (FORMAT json) to work — the server does not allow it. For a laptop-side .sql backup or a same-engine move, use Dump / PostgreSQL → PostgreSQL migrate instead.
5. Inspect the plan with visual EXPLAIN ANALYZE
For a SELECT (or another statement you want to plan), use Explain in the workbench. HiDataLinker v1.3.0 renders a visual plan. The optional Actually run control uses EXPLAIN (ANALYZE, BUFFERS, ...) inside a transaction that is then rolled back, so writes from the analyzed statement do not persist. Sequence increments and other non-transactional side effects cannot be undone — the in-app hint says this plainly.
That is the honest hook for a PostgreSQL 19 EXPLAIN ANALYZE GUI: you write the new syntax yourself, then inspect scans and buffer hits visually. There is no REPACK-specific plan UI.
Source: github.com/henrybit/HiDataLinker · Overview: /db-client
HiDataLinker is a thin Tauri desktop app for PostgreSQL and MySQL — paste DATABASE_URL, keep creds local, and avoid seat / connection / tab freemium walls. Honest v1: MySQL + PostgreSQL as marketed; not a REPACK wizard, not a COPY json exporter, and not a property-graph client.
Soft next step
Need a PostgreSQL 19 desktop GUI that runs REPACK and INSERT ... ON CONFLICT DO SELECT in a SQL editor, and shows visual EXPLAIN ANALYZE / BUFFERS, without a freemium wall?
- Download: https://hidatalinker.onesolo.app/
- Source: https://github.com/henrybit/HiDataLinker