Database Technology

Amazon RDS for SQL Server 2025 introduces sp_invoke_external_rest_endpoint, allowing direct invocation of AWS services and HTTPS endpoints from within T-SQL scripts. This capability eliminates the need for intermediate application layers to trigger external actions during database transactions. The feature simplifies integrations by enabling server-side logic to interact seamlessly with the AWS ecosystem.

• Use sp_invoke_external_rest_endpoint to call AWS or HTTPS endpoints directly from T-SQL.
• Bypass application-layer intermediaries for real-time AWS service triggers.
• Enable server-side logic to interact with the AWS ecosystem during transactions.
• Simplify integration architecture by reducing code complexity and latency.

AWS outlines four specific connection pooling strategies for Amazon Aurora DSQL to mitigate overhead and adhere to the 100-connections-per-second rate limit. The guidance focuses on preventing thundering-herd reconnection storms during scaling events or failures. The post provides a production-ready checklist for configuring pools to ensure reliable performance at scale.

• Implement strategies to stay within the strict 100-connections-per-second rate limit.
• Configure pools to prevent thundering-herd storms during reconnection events.
• Use the provided checklist to tune connection pooling for production Aurora DSQL workloads.
• Reduce connection overhead to improve overall application performance at scale.

Christophe Pettus details the new file_copy_method=clone option in PostgreSQL 18, which leverages copy-on-write filesystems to duplicate large databases nearly instantly. The feature can copy a terabyte-scale database in approximately half a second, significantly outperforming traditional block-level copying. This optimization is specifically designed for environments where the underlying storage supports efficient copy-on-write semantics.

• PostgreSQL 18 introduces file_copy_method=clone for instant DB duplication
• Achieves ~0.5s copy time for 1TB databases on compatible filesystems
• Requires underlying storage to support copy-on-write (CoW) mechanisms
• Drastically reduces provisioning time for clones and backups

A malicious actor has successfully erased the complete dataset of Romania's national land registry. The incident highlights severe vulnerabilities in the system's security posture and data management practices. This event serves as a stark warning regarding the risks associated with critical government infrastructure.

• Critical government databases remain vulnerable to total data loss.
• Security audits of national registries are urgently needed.
• Incident response plans must address catastrophic wipe scenarios.
• Backup integrity and isolation are paramount for land records.

The PostGIS team has released the first beta of version 3.7.0, introducing enhancements and bug fixes since the alpha 1 release. This update requires PostgreSQL 14 through 19beta2 and GEOS 3.10 or higher, with GEOS 3.15+ recommended for full feature utilization. Support for SFCGAL 2.3.0+ is also available for advanced geometric operations.

• Requires PostgreSQL 14-19beta2 and GEOS 3.10+, with 3.15+ needed for full features.
• Includes bug fixes and enhancements since PostGIS 3.7.0alpha1.
• SFCGAL features require version 2.3.0 or higher for optimal performance.
• Best paired with PostgreSQL 19 Beta2 and GEOS 3.15.0beta2 for testing.

Cornelia Biacsics details the formation of the Open Alliance for PostgreSQL Education (OAPE), a community-driven initiative launched in spring 2024. The organization aims to establish an open, vendor-neutral certification for PostgreSQL, addressing a gap in the market for standardized validation. Supported by global contributors, the program has evolved from a conceptual discussion into a structured movement over the past two years.

• OAPE provides a vendor-neutral certification path, reducing lock-in bias compared to cloud-specific credentials.
• The initiative is community-built, ensuring broad industry buy-in and diverse contributor perspectives.
• Standardized validation may become a key hiring filter for PostgreSQL roles across mixed-cloud environments.
• Practitioners should monitor OAPE for exam syllabi and study resources as the certification matures.