YugabyteDB normally uses transaction intents for distributed writes. Rows are first written as provisional records and, when the transaction commits, those writes […]
Read MoreYugabyteDB normally uses transaction intents for distributed writes. Rows are first written as provisional records and, when the transaction commits, those writes […]
Read MoreMany PostgreSQL statistics views are local to the PostgreSQL server process you are connected to. That matters in YugabyteDB because a cluster can […]
Read MoreYSQL uses PostgreSQL’s system catalog caches to avoid repeatedly reading metadata from the distributed system catalog. But there is another useful optimization […]
Read MoreYSQL relies heavily on PostgreSQL-compatible system catalogs to store metadata about tables, columns, indexes, constraints, functions, statistics, schemas, users, and much more. […]
Read More