Reported evidence
read_research_rows chunked reader → depends on → Read-only PostgreSQL Repeatable Read transaction
The deployed approach places related reads in one read-only Repeatable Read transaction to maintain a consistent snapshot across multiple queries. The caller, not the reading function, manages the transaction boundary.
Read the evidence
PostgreSQL’s Repeatable Read provides a consistent snapshot for reads within a transaction; this site placed list, detail, and associated-evidence reads in the same read-only Repeatable Read transaction.[S1][S5] This reading function does not start or end transactions itself; the caller is responsible for transaction boundaries.
[S1] Aperture Intelligence [S2] Aperture Intelligence [S5] PostgreSQL Global Development Group
Read the full research