You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update follower reads docs with another case (#19953)
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.
NB. Backported to all supported versions v25.1+
From Nearest Replica | `SELECT` on `GLOBAL` table| `SELECT` with `AS OF SYSTEM TIME <historical-timestamp-function>`
21
+
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 <historical-timestamp-function>`
From Nearest Replica | `SELECT` on `GLOBAL` table| `SELECT` with `AS OF SYSTEM TIME <historical-timestamp-function>`
21
+
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 <historical-timestamp-function>`
From Nearest Replica | `SELECT` on `GLOBAL` table| `SELECT` with `AS OF SYSTEM TIME <historical-timestamp-function>`
21
+
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 <historical-timestamp-function>`
0 commit comments