Hmm. Doesn't it work to ignoring tli then? All segments that their segment number is equal to or larger than the checkpoint locaiton are preserved regardless of TLI?
If we ignore TLI there is a chance that we may retain some unnecessary (or just wrong) files.
> Also, we need to take into account the divergency LSN. Files after it are > not required.
They are removed at the later checkpoints. But also we can remove segments that are out of the range between the last common checkpoint and divergence point ignoring TLI.
Everything that is newer last_common_checkpoint_seg could be removed (but it already happens automatically, because these files are missing on the new primary).
WAL files that are older than last_common_checkpoint_seg could be either removed or at least not copied from the new primary.
The current implementation relies on tracking WAL files being open while searching for the last common checkpoint. It automatically starts from the divergence_seg, automatically finishes at last_common_checkpoint_seg, and last but not least, automatically handles timeline changes. I don't think that manually written code that decides what to do from the WAL file name (and also takes into account TLI) could be much simpler than the current approach.
Actually, since we start doing some additional "manipulations" with files in pg_wal, we probably should do a symmetric action with files inside pg_wal/archive_status
