Re: Introduce XID age and inactive timeout based replication slot invalidation

> So, I think it's not a bug in the committed patch but an issue in the testing
>  venvironment. Besides, since we have not seen such failures on BF, I think it
>  may not be necessary to improve the testcases.

Thanks for your analysis!

Yes, probably WSL2/Windows interactions cause strange system clock moving.

It looks like it is a common issue with WSL2 [0].

[0]: https://github.com/microsoft/WSL/issues/10006

Best regards,

Mikhail.