> > I've also sent a diff for databases/postgresql-previous 17.10 to
> > ports@
> 
> In general, we only update postgresql-previous for issues affecting
> pg_upgrade's use of the programs. postgresql-previous is not designed
> or supported for direct use, it only exists because pg_upgrade depends
> on it.

imho it's easier to update than it is to look through the commit
history and decide whether some changes means that it's necessary.

https://www.postgresql.org/docs/release/17.8/ - some around WAL might
be relevant at first glance, looking closer I think probably not,
but I'm not sure

https://www.postgresql.org/docs/release/17.9/ - Fix failure after
replaying a multixid truncation record from WAL that was generated by an
older minor version - not sure but maybe?