PostgreSQL backup and replication work, QEMU arch updates

PostgreSQL hackers pushed forward on backup verification, logical replication logging, and extension policy while QEMU developers refined LoongArch and aarch64 virtualization support. The densest threads centered on integrity checks and conflict visibility for production databases.

Truncated compressed backup detection fixed

A patchset on the pgsql-hackers list corrects pg_verifybackup so it properly detects truncated backups compressed with zstd, gzip, or lz4. Reviewers examined the changes together with new tests across 28 messages. The fix matters for operators who rely on automated backup validation to catch incomplete archives before restore.

Conflict log table for logical replication

PostgreSQL developers reviewed version 77 of patches that introduce a conflict log history table for logical replication. Discussion among 13 participants addressed tuple size limits and JSON serialization edge cases. The feature gives administrators a durable record of replication conflicts instead of relying solely on transient logs.

Policy for abandoned PGXN extensions

David Wheeler proposed a formal policy for abandoned extensions on PGXN after recent security reports. Tom Lane and other pgsql-hackers participants weighed vetting procedures and the impact on end users. Clear rules would reduce the risk of unmaintained code remaining discoverable in the extension network.

LVZ support added to LoongArch TCG

A 23-patch series at version 5 on qemu-devel adds LVZ extension support to LoongArch TCG. The work enables nested KVM-on-TCG emulation. Two developers iterated on the series, expanding QEMU nested virtualization options for that architecture.

Customizable aarch64 KVM host model

Version 10 of a 26-patch kvm/arm series introduces a customizable aarch64 KVM host model in QEMU. It exposes writable ID register field properties on the host vCPU model. The change improves migration flexibility for aarch64 guests by letting the host model be tuned more precisely.