On Wed, Feb 18, 2026 at 5:40 AM Fabrice Chapuis <[email protected]> wrote: > why walsummarizer works fine on the primary and it is stuck on the secondary?
I don't know. It sounds like a bug, but I'm not exactly sure what the bug is. In the situation you describe here, it seems like the standby might have switched from timeline 6 to some newer timeline, most likely 7, but the WAL summarizer got stuck at the end of timeline 6 instead of following the timeline change. If that were the explanation, then this would only happen when a new primary is promoted and a standby starts following it. It could either be the case that this happens every single time a standby changes timelines, or it could be that it only happens if the standby changes timelines and some other unknown condition is also satisfied. Alternatively, maybe there's some other triggering event altogether. Any ideas, based on your experience so far? -- Robert Haas EDB: http://www.enterprisedb.com
