QEMU block fixes and PostgreSQL integrity patches

QEMU developers landed security and correctness fixes across block drivers and device models, while PostgreSQL contributors advanced patches for tuple corruption, backup consistency, and logical replication. The day centered on reliability work that affects virtualization hosts and production database deployments.

QEMU QED cluster calculation CVE fixed

QEMU merged a pull fixing an incorrect denominator in qed_bytes_to_clusters() in the QED driver. The change closes a heap memory leak reachable by the guest and is tracked as CVE-2026-118594. Operators running QED images should take the update to limit guest-visible memory exposure.

Preallocate filter data-loss races addressed

A thirteen-patch series corrects data loss in QEMU's preallocate filter. Races between multi-AioContext writes and preallocation state could drop or corrupt data. Users who rely on the filter for sparse or preallocated images gain more predictable I/O behavior under concurrency.

QOM properties tied to QAPI schema types

A sixty-five-patch v7 series links QOM and qdev properties to QAPI schema types. It introduces qapi-type introspection and deprecates older string-based property handling. The change improves type safety and long-term maintainability of device and object configuration in QEMU.

PostgreSQL ctid corruption after GiST KNN

A patch supplies the missing tts_tid in ExecForceStoreHeapTuple. Without it, FOR UPDATE after GiST KNN scans produced ctid corruption, unexpected table extension, and invalid pages. Installations that combine spatial indexes with concurrent updates should treat the fix as a data-integrity priority.

Conflict log history for logical replication

Review continues on a proposed conflict log history table for PostgreSQL logical replication. Discussion spans error handling, GUC controls, and edge cases. The table would give operators a durable record of replication conflicts instead of transient log messages.

pg_control handling in base backups

Work to return pg_control from pg_backup_stop and avoid torn control files during base backup was split for safer backpatching. Buildfarm segfaults appeared after the change landed. Consistent control-file state remains essential for reliable cluster recovery.

Secure marking for user-creatable devices

A twenty-eight-patch series marks selected user-creatable devices as secure for virtualization. The markings define clearer security boundaries for KVM and Xen guests. Host administrators gain an explicit list of devices considered appropriate for guest exposure.

Subscription two_phase state reset avoided

A patch stops ALTER SUBSCRIPTION from resetting two_phase state to pending when the feature is already enabled. The incorrect reset could break prepared-transaction checks. Logical-replication setups that use two-phase commit benefit from stable state tracking.