ArmorDB Blog
Tech-News & Trends
Current database news, release notes, and trend-driven updates with an eye on how they affect managed PostgreSQL teams.
PostgreSQL 18 Parallel GIN Index Builds: What Changes for JSONB and Search
PostgreSQL 18 can build GIN indexes in parallel, which changes how teams should plan large JSONB, array, and full-text index migrations.
PostgreSQL 18 ANALYZE VERBOSE: Better Maintenance Observability
PostgreSQL 18 adds WAL, CPU, and read detail to ANALYZE VERBOSE, giving production teams a clearer view of table statistics maintenance.
PostgreSQL 18 COPY REJECT_LIMIT: Safer Bulk Imports
PostgreSQL 18 adds REJECT_LIMIT for COPY FROM with ON_ERROR ignore, giving bulk imports a safer boundary between useful cleanup and silent data loss.
PostgreSQL 18 I/O Observability: What the New pg_stat_io Metrics Change
PostgreSQL 18 adds byte-level pg_stat_io metrics and WAL I/O visibility. Learn what changed, how to read the new counters, and what managed PostgreSQL teams should monitor after upgrading.
PostgreSQL 18 MD5 Password Deprecation: How to Move to SCRAM
PostgreSQL 18 deprecates MD5-encrypted passwords; here is how to audit roles, move to SCRAM-SHA-256, and avoid surprise login failures.
PostgreSQL 18 Logical Replication for Generated Columns: What Changed
PostgreSQL 18 can publish stored generated columns through logical replication; here is what managed PostgreSQL teams should test before using it in migrations or integrations.
PostgreSQL 18 OLD and NEW RETURNING: Cleaner Change Capture in SQL
PostgreSQL 18 lets INSERT, UPDATE, DELETE, and MERGE return OLD and NEW row values directly. Learn what changed, where it helps, and how to use it safely.
PostgreSQL 18 pg_upgrade Statistics: Safer Major Upgrades
PostgreSQL 18 lets pg_upgrade retain most optimizer statistics. Learn what changes, what still needs ANALYZE, and how to update a production upgrade runbook.
PostgreSQL 18 Temporal Constraints: What WITHOUT OVERLAPS and PERIOD Change
PostgreSQL 18 adds temporal primary keys, unique constraints, and foreign keys. Here is what changed, when to use them, and what to test before production.
PostgreSQL 18 Virtual Generated Columns: What Changed and When to Use Them
PostgreSQL 18 makes virtual generated columns the default. Learn how virtual and stored generated columns differ, what to test, and how to write safer migrations.
PostgreSQL 18 Skip Scan: What It Changes for Multicolumn Indexes
PostgreSQL 18 can use skip scan lookups on multicolumn B-tree indexes in more cases. Here is what to test before changing production indexes.
PostgreSQL 18 Asynchronous I/O: What It Changes for Managed Databases
PostgreSQL 18 adds asynchronous I/O for scans and vacuum work. Here is what the change means, when it helps, and how managed PostgreSQL teams should evaluate it.
PostgreSQL 19 Beta 1: What Managed PostgreSQL Teams Should Test Now
PostgreSQL 19 Beta 1 previews changes in maintenance, replication, security, and observability that managed PostgreSQL teams should evaluate before the final release.
PostgreSQL 18 Enables Data Checksums by Default: What Changes in Production
PostgreSQL 18 enables data checksums by default for new clusters. Here is what that means for corruption detection, upgrades, managed PostgreSQL, and rollout planning.
PostgreSQL 18 Adds OAuth 2.0 Authentication for Database Logins
Why PostgreSQL 18’s new OAuth 2.0 authentication path matters for managed PostgreSQL teams that want less password sprawl and a cleaner service identity story.
PostgreSQL 18’s uuidv7() Makes Time-Ordered UUIDs a Better Default
Why PostgreSQL 18’s new uuidv7() function matters for primary keys, B-tree locality, and managed PostgreSQL rollout decisions.
PostgreSQL 18: What the New Release Means for Managed PostgreSQL Teams
A current release-driven guide on what PostgreSQL 18 changes for managed PostgreSQL planning, compatibility, and upgrade strategy.
Keep reading across the ArmorDB blog.
Browse practical PostgreSQL guides by format, from release-driven news to deep technical operations articles.
This archive helps readers find the exact content format they need: long-form analysis, quick fixes, structured comparisons, or current release-driven news. It also gives the daily automation a stable SEO destination for each content type.