Repacking while application work continues

REPACK rewrites a table to return unused storage and can order rows using an index. The CONCURRENTLY option permits ongoing reads and writes, but the documentation lists restrictions, including partitioned and unlogged tables. DDL during the operation can prevent completion.

Our reading is that concurrent maintenance should be evaluated for the exact relation and deployment, rather than treated as a blanket promise of disruption-free administration. Storage reclamation and query performance are related but different goals: a cleaner physical layout does not, by itself, prove a faster application query.

Plan advice adds explicit control

The pg_plan_advice extension lets administrators influence planning. Once loaded, EXPLAIN supports a PLAN_ADVICE option. The documentation describes system-wide, session-preload and individual-session loading paths; deployment therefore depends on how the module is enabled.

This creates a more explicit intervention point when a chosen plan is unsuitable. Our assessment is that recorded advice should be tested with representative data and parameters. Stabilizing one observed plan is not the same as establishing that it remains the best choice as the workload evolves.

Standby reads gain a synchronization tool

The release announcement describes WAIT FOR LSN, allowing a standby session to wait for replay to a specified write-ahead-log position before reading. It also introduces logical replication of sequence values.

The architectural implication is more precise coordination between a write and a subsequent read on another server. An application still needs to know which position matters and how to handle waiting. The command should not be interpreted as making every replica automatically current at all times.

Major-version migration remains separate work

The release notes require dump and restore, pg_upgrade or logical replication when migrating from an older major version. They also document compatibility changes, including JIT being disabled by default and warnings after successful MD5 authentication.

Our conclusion is to separate feature evaluation from migration readiness. A useful rehearsal preserves the application’s queries, extensions and operational checks while establishing whether changed defaults affect its behaviour. We have not upgraded a database or reproduced project performance claims; this report describes documented release behaviour and its practical boundaries.