From c3485593759f070f75ad4bbc8e82c34bfac9d7e5 Mon Sep 17 00:00:00 2001 From: Rich Loveland Date: Thu, 17 Jul 2025 12:01:26 -0400 Subject: [PATCH] Update follower reads docs with another case Specifically, add the case that strong follower reads can occur under specific conditions even if you are not doing `SELECT ... AS OF SYSTEM TIME` or reading from a `GLOBAL` table. --- src/current/v25.3/follower-reads.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/v25.3/follower-reads.md b/src/current/v25.3/follower-reads.md index 855fafdd043..b1c228d64a5 100644 --- a/src/current/v25.3/follower-reads.md +++ b/src/current/v25.3/follower-reads.md @@ -18,7 +18,7 @@ The following table summarizes the read types and how to accomplish them. | Strong Reads | Stale Reads -----|-----------|---------------------------------------------------------------- Only From Leaseholder | `SELECT` | N/A -From Nearest Replica | `SELECT` on `GLOBAL` table | `SELECT` with `AS OF SYSTEM TIME ` +From Nearest Replica | `SELECT` on a `GLOBAL` table *or* a long-running `SELECT` whose read timestamp has fallen behind the [closed timestamp]({% link {{ page.version.version }}/architecture/transaction-layer.md %}#closed-timestamps) | `SELECT` with `AS OF SYSTEM TIME ` ## Stale follower reads