Major - P3 The current logic informing full update from the history store modify updates are not handled for non-timestamp tables. The code needs to be fixed as below to handle it for non-timestamp tables.
| Read / update type | Full / standard update | Modify |
|---|---|---|
| With timestamp | Ordinary read would find the right value in history if tombstones / stop time pairs used normal visibility rules | Ordinary read finds the oldest modify, uses its stop timestamp to skip forwards |
| Without timestamp | Ordinary read would find the right value in history | Could use the same trick as above if extended to use the stop time pair (stashing the application's snapshot info, setting snap_min = snap_max = stop_txn and snapshot_count = 0. |