You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Avoid bogus "out-of-sequence timeline ID" errors in standby-mode.
When startup process opens a WAL segment after replaying part of it, itvalidates the first page on the WAL segment, even though the page it'sreally interested in later in the file. As part of the validation, it checksthat the TLI on the page header is >= the TLI it saw on the last page itread. If the segment contains a timeline switch, and we have alreadyreplayed it, and then re-open the WAL segment (because of streamingreplication got disconnected and reconnected, for example), the TLI checkwill fail when the first page is validated. Fix that by relaxing the TLIcheck when re-opening a WAL segment.Backpatch to 9.0. Earlier versions had the same code, but before standbymode was introduced in 9.0, recovery never tried to re-read a segment afterpartially replaying it.Reported by Amit Kapila, while testing a new feature.