FLS11 — the cache CANNOT leak across users (3.3), proven at the mechanism level. Server slots
are segmented by field-security fingerprint, as they are by row-level security: each permission
class reads and fills its own slot. So: the writer's cold query writes a slot carrying the
column; the reader's identical query is NOT served from it — it writes its own segment — and
comes back without the denied column; the reader's repeat read is served from that segment
(no new write) and is still clean; and the writer's repeat read still gets the column, so the
reader's miss never narrowed the writer's slot.
FLS11 — the cache CANNOT leak across users (3.3), proven at the mechanism level. Server slots are segmented by field-security fingerprint, as they are by row-level security: each permission class reads and fills its own slot. So: the writer's cold query writes a slot carrying the column; the reader's identical query is NOT served from it — it writes its own segment — and comes back without the denied column; the reader's repeat read is served from that segment (no new write) and is still clean; and the writer's repeat read still gets the column, so the reader's miss never narrowed the writer's slot.