OffNet Newsroom

Daily topic roundup

Database Technology

Monday, August 31, 2026 · 5 stories, curated & summarized — click any story for the source.

ReToolSQL introduces a two-stage training framework that combines supervised fine-tuning on rejection-sampled traces with agentic reinforcement fine-tuning over multi-turn tool-use. This approach addresses the limitation of single-turn SQL generation by allowing models to iteratively refine queries based on execution feedback. The method enables smaller models to match or exceed larger systems by leveraging complementary learning axes.

  • Multi-turn agentic RL allows iterative error recovery in SQL generation.
  • Smaller models can outperform larger systems using this two-stage framework.
  • Rejection-sampled reasoning traces provide a strong supervised warm-start.
  • Tool-use trajectories enable robust execution feedback loops.
HOW IT WORKSReToolSQL Training Pipeline1Generate rejection-sampled traces2Supervised fine-tuning warm-start3Agentic multi-turn refinement4Reinforcement learning tuning

Fabiane Nardon outlines how TOTVS prepares enterprise data for AI agents by balancing deterministic logic with non-deterministic LLMs. The approach leverages data mesh, low-latency database architectures, and semantic ontologies to optimize context windows. Dynamic MCP tool selection is employed to reduce token overhead while maintaining precision and security.

  • Balance deterministic logic with LLMs for precision, security, and cost control
  • Use semantic ontologies and data mesh to structure enterprise data for AI
  • Implement low-latency DB architectures to support real-time agent interactions
  • Leverage dynamic MCP tool selection to minimize token overhead in context windows
  • Prioritize token efficiency to reduce costs in transactional systems

Christophe Pettus clarifies three key GUC parameters that dictate server log content: the severity floor, the inclusion of triggering SQL, and the verbosity of message fields. These settings work in tandem to filter and format diagnostic output. Understanding their interaction is critical for tuning log granularity without overwhelming storage or obscuring errors.

  • log_min_messages sets the severity threshold for what gets logged at all.
  • log_min_error_statement determines if the offending SQL is appended to errors.
  • log_error_verbosity controls the number of detail fields in each log message.
  • These three GUCs must be tuned together for effective diagnostic logging.
Hacker News (100+ points) general

Achieving P99 0ms autocomplete across 240M domain names

The article details a system capable of returning autocomplete suggestions for 240 million domain names with a P99 latency of 0 milliseconds. This performance is achieved through specialized data structures and caching strategies optimized for massive scale lookups. The approach demonstrates how to minimize tail latency even when dealing with extremely large datasets in real-time applications.

  • Optimized data structures enable sub-millisecond lookups at massive scale.
  • Caching strategies are critical for maintaining P99 0ms latency.
  • System design must prioritize tail latency over average performance.
  • Real-time autocomplete can handle 240M entries without degradation.
BY THE NUMBERSZero Latency at Massive Scale0msP99 Latency for 240M DomainsAchieved through optimized data structures and caching
AWS What's New awsdatabase ↺ since 08-29

Amazon Aurora MySQL 3.13 GA with MySQL 8.0.45 compatibility

Amazon Aurora MySQL-Compatible Edition 3 has reached general availability for version 3.13, aligning with MySQL 8.0.45. This release incorporates community MySQL fixes alongside Aurora-specific performance and stability improvements. The update is available in all AWS Regions where Aurora MySQL is currently supported.

  • Upgrade via automatic minor version updates during scheduled maintenance windows.
  • Perform in-place upgrades or use snapshot restore methods for changes.
  • Leverage AWS Organizations Upgrade Rollout Policy for phased cluster updates.
  • Review Aurora MySQL 3 and MySQL 8.0.45 release notes for specific changes.
CHECKLISTUpgrade Steps for Aurora 3.13Upgrade via automatic minor updates during maintenancePerform in-place upgrades or snapshot restoreUse AWS Organizations for phased rolloutReview release notes for specific changes
↑