Thomas Munro <thomas.munro@gmail.com> writes:
> Alright, I've pushed a change like that. Let's see if that clears it
> up.
Nope:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2022-01-18%2019%3A50%3A57
That reloptions test has been there awhile, and we weren't seeing
issues with it before. What about the replication environment
would cause VACUUM to behave differently? Maybe it thinks there
are non-removable tuples because the walsender is holding back
global xmin?
regards, tom lane
