The latest YugabyteDB preview release supports PostgreSQL 15. This represents a significant upgrade from the previous version. YugabyteDB 2.25 brings many new, long-awaited features, and this blog discusses the top 15 features (from PG12 to PG15) that will significantly benefit YugabyteDB developers.
Amazon recently launched Aurora DSQL, a new distributed SQL database that validates the growing importance of distributed SQL and introduces unique architectural features tied to the AWS infrastructure. This blog examines Aurora DSQL’s PostgreSQL compatibility, architectural distinctions, concurrency control, multi-region capabilities, and positioning relative to YugabyteDB in the evolving database landscape.
AWS Time Sync Service and Amazon EC2 utilize hardware and software solutions to facilitate the use of Precision Hardware Clocks (PHC) through Network Time Protocol (NTP) or Precision Time Protocol (PTP). Discover how YugabyteDB leverages this technology to maintain consistency at high-performance levels.
YugabyteDB’s introduction of in-place index updates is a significant improvement to PostgreSQL’s traditional index and table update mechanics. This blog examines how YugabyteDB modified the storage layer of PostgreSQL and how this enhancement delivers enhanced performance.
Database High Availability has traditionally been achieved through enhanced and automated disaster recovery solutions. Although these measures reduce the impact of failures, they still result in complete downtime for the application during the failover process. In this blog, we compare this approach with cloud-native solutions for high availability, focusing on resiliency built directly into the database.
Optimizing SQL indexing involves carefully considering the column order, understanding index scan ranges, and leveraging the index scan capabilities of your database to ensure efficient query performance. Discover how you can do this effectively by following the steps laid out in this new ‘How to’ guide.
PgBench is widely used for testing database performance, but its default ‘TPC-B like’ workload may not accurately represent true performance. To achieve more realistic load testing, users can employ custom SQL scripts within PgBench. In this demonstration, we’ll show how these adjustments work using YugabyteDB.
YugabyteDB’s automatic sharding overcomes PostgreSQL’s partition key limitations by allowing date range queries without modifying table partitioning. Thanks to its global secondary indexes, which don’t require a shared sharding key, YugabyteDB enhances performance by distributing rows across multiple servers. Discover the full advantages and see step-by-step instructions in our latest blog post.
Managing large PostgreSQL tables requires partitioning, which can complicate queries. Migrating to YugabyteDB simplifies scaling by automatically sharding and distributing data and minimizing partition reliance. The article includes demos on PostgreSQL’s partitioning limitations and YugabyteDB’s advantages in distributed tables and scalability.
PostgreSQL offers robust features but has certain limitations in scalability, replication, resilience (and more). YugabyteDB addresses these issues through distributed design, storage efficiency, and transaction handling, providing a comprehensive solution when high availability, ACID, and scale are mandatory.
