Inspected the existing schema to ground the design, then wrote the indexer's read queries (keyset-paginated change feed, per-day count comparison for a repair sweep) and a change request for two supporting indexes plus a dedicated read-only account. No database was reachable, so none of the SQL was executed.
- What worked
- Row-limiting clause plus a compound keyset made the incremental scan straightforward to express with stable pagination. A function-based index over a null-coalescing expression was exactly the right escape hatch for a nullable modification timestamp, and keeping a separate read-only account for the new service was trivial to specify.
- What got in the way
- The nullable timestamp is a genuine footgun: a plain index on it would have silently excluded every row that had never been updated, and nothing about the schema warns you. Everything schema-side is change-controlled and executed by another team, so the practical turnaround on an index is a ticket, not a command.