March 2025 Summaries
2 posts from Yugabyte
Filter
Month:
Year:
Post Summaries
Back to Blog
YugabyteDB Voyager is an open-source migration tool that simplifies the complex task of transitioning from single-node databases like PostgreSQL or Oracle to the distributed YugabyteDB system. It generates a comprehensive assessment report that evaluates migration complexity, identifying unsupported features and syntax incompatibilities, and offering workarounds where possible. The tool calculates a 'Migration Complexity' rating, ranging from LOW to HIGH, based on these incompatibilities and their impacts. Additionally, it provides guidance on cluster sizing and sharding, offering resource estimations and optimal configurations for the YugabyteDB cluster, including node count, vCPU, and memory requirements, tailored to the database's table sizes and throughput needs. This analysis enables users to anticipate migration challenges and prepare accordingly, ensuring a smoother and more efficient transition process.
Mar 28, 2025
629 words in the original blog post.
Mark Peacock's blog post delves into optimizing correlated subqueries using Semi Joins in PostgreSQL and YugabyteDB. He encountered performance issues with a query due to inefficient execution of correlated subqueries, which involved nested loop overhead. By analyzing the execution plan with EXPLAIN ANALYZE, Peacock identified that restructuring the query to reposition the correlation predicate from the JOIN condition to the WHERE clause allowed PostgreSQL’s optimizer to recognize the EXISTS condition as eligible for a Semi Join. This structural change enabled more efficient execution by reducing overhead and improving index usage, ultimately allowing the database to filter rows earlier. The blog highlights the nuances between ANSI and pre-ANSI syntax, emphasizing that pre-ANSI syntax offers more flexibility in optimizing joins. Peacock's experience underscores the importance of understanding PostgreSQL's handling of EXISTS clauses and the benefits of query restructuring in achieving optimal performance.
Mar 20, 2025
1,180 words in the original blog post.