Database Technology

Dave Stokes shares a tutorial on importing the Northwind database into PostgreSQL using DBeaver Enterprise Edition 26.1.0. He downloads the SQL schema from a GitHub repository and opens it directly in the client to facilitate SQL learning. This process demonstrates a straightforward method for setting up demo databases on PostgreSQL.

• Northwind is a cross-platform demo DB, originally Microsoft, now easily available for PostgreSQL.
• Use DBeaver Enterprise 26.1.0 to open and execute the northwind.sql script directly.
• GitHub repository pthom/northwind_psql hosts the required SQL schema file.
• Tutorial presented at Texas Linuxfest on Nov 6th for SQL skill development.

Amazon Aurora MySQL-Compatible Edition 8.4.8 is now generally available, bringing security enhancements and bug fixes alongside key functional improvements. The release adds support for post-quantum TLS key exchange to secure data in transit, configurable transaction timeouts to mitigate InnoDB purge blocking, and multi-source replication for consolidating data from multiple sources. Additionally, delayed replication is introduced to protect against accidental data loss by allowing configurable replication lag.

• PQ-TLS support enables post-quantum cryptography for data-in-transit encryption.
• Transaction timeouts prevent long-running transactions from blocking InnoDB purge operations.
• Multi-source replication allows merging shards and consolidating data into a single replica.
• Delayed replication provides protection against accidental deletions or errors via configurable lag.
• Upgrade to Aurora MySQL 8.4.8 to access these security and reliability features.

Fleet impact: This release is critical for Aurora MySQL fleets requiring enhanced security posture via PQ-TLS and improved operational resilience through multi-source replication and delayed replication. DBAs managing sharded architectures should evaluate multi-source replication for consolidation tasks, while those concerned with accidental data loss should configure delayed replicas immediately. Ensure application connection libraries support PQ-TLS if enabling this feature.

Amazon RDS for SQL Server now supports 18 additional SQL trace flags, accessible via database parameter groups. These flags allow DBAs to modify engine behaviors such as query optimizer cardinality estimation, lock escalation, and memory handling. This update provides greater flexibility to optimize performance and stabilize workloads directly within the managed environment without requiring infrastructure changes.

• Enable 18 new trace flags (e.g., 647, 3654, 11024) via RDS parameter groups.
• Fine-tune query optimizer behavior and cardinality estimation for better plans.
• Address specific workload challenges like lock escalation and DDL performance.
• No need for unmanaged instances to apply these engine-level configuration switches.
• Review flags like 9481/9492 for compatibility mode adjustments if needed.

Fleet impact: RDS SQL Server DBAs can now resolve specific performance issues or optimizer quirks that previously required migration to EC2 or custom instances. Check parameter group settings for flags like 9481 (compatibility mode) and 11024 (tempdb allocation) to see if they apply to current workload bottlenecks.

PostgreSQL offers a set of legacy GUCs including log_parser_stats, log_planner_stats, log_executor_stats, and log_statement_stats. These parameters record crude but essential metrics like CPU time, page faults, and context switches for individual statements. They remain an irreplaceable tool for diagnosing the specific resource bottlenecks behind slow queries.

• Use log_executor_stats to isolate execution-level CPU and IO costs per statement.
• Monitor log_parser_stats and log_planner_stats to identify overhead in query analysis phases.
• These metrics reveal context switches and page faults often hidden by higher-level stats.
• Enable selectively for specific queries to avoid excessive logging overhead in production.

PostgreSQL 19 Beta 3 was released on August 13, 2026, with general availability expected in the coming weeks. The release notes highlight specific compatibility breaks that may impact existing applications and introduce new SQL features. This overview focuses on practical changes rather than a full changelog dump.

• PostgreSQL 19 GA is likely within weeks, following the typical September/October release cadence.
• Several compatibility breaks are present that require careful review of existing application code.
• New SQL-level additions have been identified as genuinely useful for query optimization.
• All examples and syntax checks were performed against a live PostgreSQL 19 Beta 3 instance.