ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
Goal Determine whether a committed YSQL ALTER TABLE can be safely rolled back in YugabyteDB 2.x after the distributed master catalog and tablet leaders adopt the new catalog version. Constraints and uncertainty Online DDL is applied incrementally across tablets rather than as a single-node atomic commit, so clients attached to different nodes can temporarily
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 YSQL inherits PostgreSQL date/time semantics for a multi-region deployment that needs regional reporting while keeping storage consistent. The design goal is to store absolute instants uniformly and render local wall-clock values per client region without introducing DST or offset drift in cross-region aggregates. Constraints are session-scoped. t
YugabyteDB provides a PostgreSQL-compatible YSQL interface where schema changes are processed via DocDB. While adding a column with a constant default is typically handled as an online metadata update, the behavior changes when volatile expressions are used as defaults. When a column is added with a volatile default—such as a function returning a timestamp o
yugabytedb