Technology1 min read

PostgreSQL 19: A hands-on tour with runnable browser examples

By · Published by Everything Blog

In short

Released on November 19, 2026, version 19.0 brings a native REPACK command that rewrites tables to release unused storage back to the operating system. A concurrent mode utilizes logical decoding to track ongoing modifications, minimizing downtime by securing only a brief access-exclusive lock during the final swap. Hands-on testing is supported via a "blog_lab" demo database configured for the "student" user. This sandbox features a multi-port environment including a primary instance, an on-demand logical subscriber, and a physical standby.

Key points

  • New SQL additions include planner advice, range subtraction, get-or-create inserts, IGNOR…: New SQL additions include planner advice, range subtraction, get-or-create inserts, IGNORE NULLS, and updated JSON handling.
  • Administrators can reclaim physical disk capacity directly without relying solely on stan…: Administrators can reclaim physical disk capacity directly without relying solely on standard vacuum operations that merely prepare space for reuse.
  • Users can safely evaluate replication setups using preconfigured ports for primary, logic…: Users can safely evaluate replication setups using preconfigured ports for primary, logical subscriber, and physical standby instances.

Sources checked by our analysis pipeline: 1

PostgreSQL 19: less friction, more control

Run the new SQL, inspect the planner, and replicate between real PostgreSQL 19 servers.

A release you can try at the prompt

PostgreSQL 19 brings useful new SQL alongside maintenance and replication improvements. Try IGNORE NULLS, get-or-create inserts, JSON export, JSONPath transformations, and range subtraction, then explore planner advice and real replication.

PostgreSQL 19.0 · released 19 November 2026. The stable release announcement introduces the version installed in this sandbox. Each feature links to its official documentation. The release notes remain the complete change log.

About this terminal. Experiments run on a real PostgreSQL 19 server as student

, in a disposable guest. Maintenance tables live in blog_lab

. Replication experiments start additional real servers on demand: a logical subscriber on 5433, and a physical standby on 5434, both fed by the primary on 5432. To fit the guest’s memory budget, only one of these extra instances runs at a time: each replication card stops the other and starts its own. Re-run that card before checking its current state again. Their first runs take…

Technology