ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use YugabyteDB follower reads for staleness-tolerant SELECTs to reduce leader load, but avoid them for reads that must reflect immediately committed writes.
Learn how to use YSQL range partitioning in YugabyteDB 8.0+ to eliminate write hotspots and distribute time-series data across cluster nodes while maintaining ACID compliance.
A decision guide for picking YSQL or YCQL in YugabyteDB, covering consistency models, performance trade-offs, and a concrete validation workflow for test clusters.
YugabyteDB 2.12+ can run ADD COLUMN and similar DDL online by keeping dual schema versions and coordinating the change across tablets with two-phase commit, with limits for primary key and data type rewrites.
Follower reads route SELECT queries to nearby replicas, cutting cross-region read latency at the cost of a configurable staleness bound (default 30 s). Enable it with yb_read_from_followers, verify with a benchmark, and keep leader reads for read-after-write consistency.
Follower reads let a YugabyteDB session read from a local Raft follower instead of a cross-region leader. Here's the trade, a worked YSQL example, and how to verify it.
Learn how YugabyteDB follower reads let you serve SELECT queries from replica tablets to cut read latency, with a concrete example, setup steps, and consistency trade‑offs.
Goal Determine if the PostgreSQL JDBC driver 42.4.x can successfully negotiate the YSQL wire protocol with a YugabyteDB 2.x cluster, and identify any configuration options that enable legacy protocol support. Constraints & Uncertainty YugabyteDB 2.x implements the PostgreSQL 14 wire protocol, which is officially supported only by JDBC drivers 42.5.x and
When using YSQL follower reads in YugabyteDB, the goal is to achieve read scaling while maintaining a predictable bound on data staleness. The current implementation relies on an internal lag heuristic to decide when to redirect a follower‑read query to the leader, but this threshold is not exposed as a configurable GUC or visible metric, leaving operators u
yugabytedb