On Sat, Sep 10, 2022 at 5:44 PM Justin Pryzby <pry...@telsasoft.com> wrote: > < 2022-09-09 19:37:25.835 CDT telsasoft >ERROR: MultiXactId 133553154 has > not been created yet -- apparent wraparound
I guess what happened here is that after one of your (apparently several?) OOM crashes, crash recovery didn't run all the way to the true end of the WAL due to the maintenance_io_concurrency=0 bug. In the case you reported, it couldn't complete an end-of-recovery checkpoint until you disabled recovery_prefetch, but that's only because of the somewhat unusual way that vismap pages work. In another case it might have been able to (bogusly) complete a checkpoint, leaving things in an inconsistent state.
