On 21/09/2026 07:43, Naga Appani wrote:
I did not add the start-of-recovery initialization from the control file Heikki mentioned [0]. With only the redo-path update there is still a short window before the first truncation record is replayed where oldestOffset reads 0. Handling that at startup needs the value without the find_multixact_start() lookup, which asserts finishedStartup, so I left it out for now.
Hmm, the window could be very long, there's no guarantee that you'll see a MULTIXACT_TRUNCATE_ID record any time soon. And after restart, it'll revert back to 0 again. If we can't get a reasonable value at startup, I wonder if we should just always show NULL in the standby.
- Heikki
