OffNet Newsroom

Daily topic roundup

Database Technology

Sunday, August 30, 2026 · 6 stories, curated & summarized — click any story for the source.

TOTVS engineer Fabiane Nardon outlines strategies for preparing enterprise data for token-intensive AI agents. The approach balances deterministic transactional logic with non-deterministic LLMs by leveraging data mesh, low-latency database architectures, and semantic ontologies. Key tactics include dynamic MCP tool selection to optimize context windows and significantly reduce token overhead.

  • Use semantic ontologies to map transactional data for efficient LLM context retrieval.
  • Implement dynamic MCP tool selection to manage agent interactions and reduce latency.
  • Balance deterministic logic with non-deterministic models to ensure security and precision.
  • Optimize context windows to lower token costs in high-volume transactional systems.

Christophe Pettus explains that the log_line_prefix GUC is the critical join key for correlating PostgreSQL log messages with external system logs. While the database generates the message body, the prefix contains all contextual metadata like session IDs, transaction IDs, and timestamps. Properly configuring this prefix is essential for effective distributed tracing and debugging across heterogeneous infrastructure.

  • The prefix is user-defined; use it to inject unique IDs for cross-system correlation.
  • Include transaction and session identifiers to link logs to specific client interactions.
  • Standardize timestamp formats to align with other services in your observability stack.
  • Treat log_line_prefix as a distributed tracing context carrier, not just metadata.
AWS What's New awsdatabase ↺ since 08-29

Amazon Aurora MySQL 3.13 GA brings 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 specific Aurora enhancements for performance and stability. Organizations can deploy this update via automatic minor version upgrades during scheduled maintenance windows or through manual in-place and snapshot restore methods.

  • Upgrades are supported in all AWS Regions where Aurora MySQL is available.
  • Use AWS Organizations Upgrade Rollout Policy to orchestrate phased cluster updates.
  • Enable automatic minor version upgrades to simplify operational overhead at scale.
  • Minor version upgrades can be performed in-place or via snapshot restore.

Fleet impact: Aurora MySQL 3.13 is a minor version upgrade within the 3.x compatible family, ensuring backward compatibility with existing MySQL 8.0 workloads. For ExaCC/RAC fleets, this is irrelevant, but for Aurora PostgreSQL/MySQL fleets, verify that application ORM drivers support the specific MySQL 8.0.45 feature set and schedule upgrades during low-traffic windows to mitigate any transient replication lag during the minor version switch.

CHECKLISTDeploying Aurora MySQL 3.13Enable automatic minor version upgradesUse AWS Organizations for phased rolloutsPerform in-place or snapshot restoreAvailable in all supported regions

Amazon RDS for PostgreSQL now supports minor versions 18.6, 17.11, 16.15, 15.19, and 14.24. These updates address Common Vulnerabilities and Exposures (CVEs) and incorporate community bug fixes and improvements. Users can apply these upgrades during scheduled maintenance windows or via automatic minor version upgrades.

  • Upgrade to latest minor versions to patch CVEs and access bug fixes.
  • Enable automatic minor version upgrades for simplified operations.
  • Use AWS Organizations Upgrade Rollout Policy for phased, safe deployments.
  • Leverage Amazon RDS Blue/Green deployments to minimize downtime.
CHECKLISTPostgreSQL Upgrade StrategyUpgrade to latest minor versions to patch CVEsEnable automatic minor version upgrades for simplicityUse AWS Organizations for phased safe deploymentsLeverage Blue/Green deployments to minimize downtime
AWS Database Blog awsdatabase ↺ since 08-27

CORTO scales Aurora PostgreSQL pgvector to 7.6B vectors for legal search

CORTO deployed Amazon Aurora PostgreSQL with pgvector to handle a production workload of 7.6 billion vectors across 2.5 billion documents. The system delivers sub-second semantic search results for over 10,000 law firms while reducing storage costs by 75%. This architecture enables high-throughput legal document retrieval at a billion-scale level.

  • Aurora PostgreSQL with pgvector supports 7.6B vectors in production without performance degradation.
  • Storage costs were reduced by 75% compared to previous solutions for legal semantic search.
  • Sub-second latency is achievable for 10,000+ concurrent law firm users.
  • The solution scales to 2.5 billion documents while maintaining rapid query response times.
AWS What's New awsdatabase ↺ since 08-28

Amazon Redshift KDS streaming now supports 10MiB records

Amazon Redshift has increased its supported record size limit for Amazon Kinesis Data Streams ingestion from 1 MiB to 10 MiB. This change aligns with the expanded maximum record size in Kinesis, allowing direct ingestion of larger payloads without the need for client-side splitting. The feature is now available in all commercial AWS regions where Redshift is deployed.

  • Eliminates the need to split large records in ingestion pipelines, reducing complexity and latency.
  • Unlocks use cases for high-volume workloads involving large individual event payloads.
  • Available immediately in all commercial AWS regions with Amazon Redshift.
  • Simplifies architecture by matching Kinesis's native 10 MiB record limit.
THE SHIFTRedshift KDS Record Size Limit1 MiBPREVIOUS LIMIT10 MiBNEW LIMITEliminates need for client-side splitting
↑