Database Technology

Google AlloyDB has generally available AI functions using a proxy model architecture that trains lightweight models directly from LLM outputs. This approach enables queries to run at database speed by eliminating external LLM calls, achieving up to 100,000 rows per second in preview. Internal benchmarks claim a 2,400x throughput improvement, though these metrics are specific to the ai.if function.

• Eliminates external API latency by running inference locally within the database engine.
• Trains lightweight proxy models from LLM outputs to handle high-volume query tasks.
• Achieves massive throughput gains (2,400x) for specific AI functions like ai.if.
• Reduces data egress costs and security risks by keeping inference inside the DB.
• Benchmark figures are internal and apply only to the ai.if function.

A new project called pgrust has rewritten the Postgres database engine in the Rust programming language. The implementation has successfully passed 100% of the standard Postgres regression test suite, demonstrating functional parity with the original C-based codebase. This milestone highlights significant progress in porting complex legacy database systems to memory-safe languages.

• Rust port achieves full regression test compliance, proving functional equivalence to C Postgres.
• Demonstrates viability of rewriting complex, legacy database engines in memory-safe languages.
• No immediate production-ready features or performance benchmarks cited in the source.
• Community interest is high, indicated by significant Hacker News engagement.

This second part of a series on Amazon RDS for Oracle read replicas details methods to monitor and resolve replication lag. It covers using CloudWatch metrics and database views to track lag, followed by wait event analysis to pinpoint root causes. The guidance focuses on troubleshooting specific performance bottlenecks to optimize replica throughput.

• Use CloudWatch metrics and DB views to monitor replication lag in real time.
• Analyze wait events to identify specific performance bottlenecks causing lag.
• Troubleshoot common root causes to resolve read replica synchronization delays.

Fleet impact: For DBAs managing Oracle ExaCC or RDS for Oracle, leverage wait event analysis to distinguish between I/O saturation and CPU contention on replicas. Prioritize tuning redo transport and applying the configuration optimizations from Part 1 to prevent lag during peak write workloads.

AWS Database Blog outlines how to leverage the redo compression feature in Amazon RDS for Oracle to reduce replication lag on standby replicas. This approach focuses on minimizing the bandwidth and processing overhead associated with transmitting redo data between primary and replica instances. The series notes that part two will address monitoring and troubleshooting strategies for lag resolution.

• Enable redo compression on RDS for Oracle replicas to shrink network payload size.
• Reduced redo volume directly lowers replication lag during high-write workloads.
• Part 1 covers the optimization mechanism; part 2 details monitoring and troubleshooting.
• Review current redo generation rates before enabling compression to gauge potential savings.

Fleet impact: For Oracle ExaCC/RAC fleets, this confirms that network bandwidth between nodes or availability zones is a key constraint for Data Guard lag; consider enabling similar compression or tuning network QoS if lag spikes occur. For AWS RDS for Oracle users, verify that the redo compression parameter is enabled and monitor replication lag metrics to ensure the feature is actively reducing the delta between primary and replica timestamps.

AWS Database Migration Service now supports CDC-only reverse replication from Amazon RDS for Db2 back to on-premises AIX Db2 instances. This capability enables organizations to maintain a synchronized copy of their cloud database on local hardware for disaster recovery scenarios. The process allows for a controlled fail-back operation without requiring full schema or data reloads.

• Enables reverse CDC replication from RDS for Db2 to on-premises AIX Db2.
• Supports disaster recovery fail-back strategies for Db2 workloads.
• Uses DMS to keep on-premises data in sync with the cloud source.
• Avoids full data reloads by leveraging continuous change data capture.