Database Technology

Amazon Aurora MySQL-Compatible Edition 8.4.8 is now generally available, bringing the underlying MySQL 8.4.8 engine to the platform. Key additions include support for post-quantum TLS key exchange, configurable transaction timeouts to mitigate InnoDB purge issues, and new replication capabilities. These replication features encompass multi-source consolidation and delayed replication for enhanced data protection and operational flexibility.

• Enable post-quantum TLS (PQ-TLS) key exchange for future-proof data-in-transit encryption.
• Use transaction timeouts to prevent long-running transactions from blocking InnoDB purge operations.
• Leverage multi-source replication to consolidate data from multiple sources into a single replica.
• Implement delayed replication with configurable lag to safeguard against accidental data loss.
• Review security enhancements and bug fixes included in this MySQL 8.4.8 compatible release.

Fleet impact: For Aurora MySQL fleets, prioritize upgrading to 8.4.8 to access PQ-TLS for compliance and transaction timeouts to stabilize InnoDB performance under heavy write loads. Evaluate multi-source replication to simplify shard merging or centralized reporting architectures, and configure delayed replicas to protect against logical corruption or accidental deletes.

Setting session_replication_role to replica only disables triggers and rules, not all constraint enforcement. As shown in the source, foreign keys and check constraints remain active because they are implemented via internal triggers that are not suppressed by this setting. Consequently, invalid data such as negative amounts or missing references will still be rejected even in replica mode.

• session_replication_role = replica does not bypass check constraints.
• Foreign keys are enforced by internal triggers that remain active.
• Data integrity checks still apply during replica-mode loads.
• Do not rely on this setting to skip all validation rules.

PostgreSQL 19 Beta 3 shipped on August 13, 2026, with general availability expected in the next few weeks. The release highlights specific compatibility breaks that may affect existing applications and introduces new SQL-level additions. These changes have been validated against a live Beta 3 instance to ensure accuracy.

• PostgreSQL 19 GA is likely within weeks, following the standard September/October cadence.
• Review release notes carefully to avoid breaking changes hidden in compatibility updates.
• New SQL features are available and tested on Beta 3 for immediate evaluation.

Christophe Pettus highlights four legacy PostgreSQL GUCs—log_parser_stats, log_planner_stats, log_executor_stats, and log_statement_stats—that expose per-statement CPU time, page faults, and context switches. These metrics provide granular, low-level performance data that remains essential for diagnosing why specific queries consume resources, despite their age. The parameters offer a crude but irreplaceable view into the internal execution costs of individual statements.

• Log four specific GUCs to capture CPU time, page faults, and context switches per statement.
• Use these metrics to diagnose high resource consumption that EXPLAIN plans cannot fully explain.
• These are legacy parameters but remain critical for deep-dive performance analysis of individual queries.
• Monitor executor and planner stats separately to pinpoint where overhead occurs in the query lifecycle.

Christophe Pettus introduces two new GUCs to expose startup phase details directly in server logs. The log_startup_progress_interval parameter allows tracking WAL replay progress on a primary instance. Meanwhile, log_recovery_conflict_waits helps diagnose standby stalls by logging specific conflict wait events.

• Track WAL replay progress on primary via log_startup_progress_interval
• Diagnose standby stalls using log_recovery_conflict_waits GUC
• Both settings expose startup internals previously hidden from logs
• Useful for debugging slow recovery or replication lag issues

The PGDG YUM repository has added Amazon Linux 2023 as a first-class target, providing native RPM packages alongside Enterprise Linux, Fedora, and SUSE. This eliminates the previous necessity of building from source or relying on outdated base repository versions for EC2 instances. Users now gain access to the full extension ecosystem and day-one minor releases consistent with other major distributions.

• EC2 PostgreSQL deployments can now use official PGDG RPMs instead of source builds or base OS packages.
• Access to the complete extension ecosystem and latest minor releases is now available on AL2023.
• Packaging consistency improves across Linux distributions, simplifying fleet management and automation.