It would catch up by reading the WAL files when it restarted - using this method, the WAL files will remain on disk until they've been read.
but, disk isn't usually infinite.
I had imagined the GP might have been insinuating something like: a configurable number of WAL files would be written, then they'll be overwritten once all full.