PostgreSQL Moves Away from MD5: Why the Authentication Scheme is Changing
MD5 has long been the standard for authentication in PostgreSQL. However, accumulated limitations have led to a gradual phasing out and a transition to a more robust model.
Databases on ThecoreGrid explores the design, operation, and scaling of data storage systems in highload and distributed environments.
We cover relational and NoSQL databases, NewSQL systems, and specialized storage engines, focusing on consistency models, replication, partitioning, and fault tolerance. Topics include query optimization, indexing strategies, transaction management, and performance tuning under real production workloads. We analyze trade-offs between strong and eventual consistency, latency and durability, and operational complexity at scale. Content includes real-world BigTech practices, incident post-mortems, and lessons from failures in distributed data systems. You’ll also find deep dives into storage internals, caching layers, data lifecycle management, and multi-region deployments. Instead of basic setup guides, the Databases tag delivers practical engineering insights for backend engineers, data engineers, architects, and SRE teams responsible for reliable, scalable, and efficient data persistence.
MD5 has long been the standard for authentication in PostgreSQL. However, accumulated limitations have led to a gradual phasing out and a transition to a more robust model.
Request timeouts do not always indicate a problem in the database. Often, degradation is hidden in the path between the application and the DB. The problem manifests when database metrics appear stable, but clients experience timeouts. At the observation level, this looks like a contradiction: latency increases while database time remains the same. The reason … Read more
Controls: ← → to move, ↑ to rotate, ↓ to drop.
Mobile: use buttons below.