Currently, no users of rangefeeds should ever see an inline value as they all operate on normal SQL tables.

If we were to run rangefeed on range with inline values, we have at least a few problems:

• Since inline values do not have associated timestamps, we currently emit all inline values encountered during a catchup scan, even if they have not changed since the given cursor.
• If the inline value changed multiple times since the checkpoint, a catchup-scan will only observe the final value.
• If a TBI is used for the catchup scan we may miss the inline value completely.

Do we have future uses for rangefeeds over ranges with inline values?

Jira issue: CRDB-9556