ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #mysql
Keep DataGrip’s page‑size limit enabled to avoid loading millions of rows into memory, and tune the JDBC fetch size per driver for smooth paging.
Choosing between MySQL’s native JSON type and fully normalized tables can save migrations but may hurt performance. This guide walks through a real‑world example, shows how to index JSON, and weighs the trade‑offs.
Decide when to split a Vitess shard and run the online reshard workflow safely.
Increase MySQL query speed by tuning the InnoDB buffer pool: choose the right size, add instances, verify hit ratios, and recover if swapping occurs. Follow our step‑by‑step guide for a dedicated server.
Large MySQL tables can slow queries, but partitioning can slice the data and speed them up. This blog walks through the problem, the right scenarios, how to choose a partition type, a step‑by‑step example, and the trade‑offs you need to watch for.
Decide between MySQL’s ON DUPLICATE KEY UPDATE, INSERT IGNORE, and REPLACE by evaluating conflict handling, performance, and data integrity. This guide offers a comparison table, trade‑offs, and a step‑by‑step validation example.
Your query uses an index but still performs too many full-row reads. MySQL's Index Condition Pushdown can filter rows inside InnoDB before fetching them—if your predicates qualify.
Learn how Vitess VReplication streams MySQL binlogs to keep source and target tables in sync, enabling online resharding without stopping traffic.
A correlated scalar subquery can turn a single-table read into repeated scans. This guide shows how to rewrite it as a window function in MySQL 8.0+, validate the plan, and recover safely.
datagrip
postgresql
json
vitess