ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
Goal Use YugabyteDB’s PostgreSQL‑compatible pg_stat_statements extension to surface the most expensive YSQL queries and verify whether the cost originates from local computation or distributed storage access before applying any index or flag changes. Constraints Statistics are per‑node, reset on restart, and add measurable overhead bounded by pg_stat_stateme
Integration of YugabyteDB YSQL authentication with JDBC connection pooling The goal is to determine how YugabyteDB’s yb‑tserver treats a role whose VALID UNTIL timestamp has passed when the client driver maintains a pooled connection that was established before expiration. Uncertainty arises because the server checks the VALID UNTIL clause at login time, but
Enforcing Uniform Credential Expiration Across YSQL and YCQL The goal is to implement a consistent least‑privilege policy that revokes user access automatically after a specified time, regardless of whether the client connects via YSQL (PostgreSQL‑compatible) or YCQL (Cassandra‑compatible). In YSQL, roles can be created with a VALID UNTIL timestamp, and auth
yugabytedb