| From: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: incremental backup issue |
| Date: | 2026-02-19 08:27:05 |
| Message-ID: | CAA5-nLCPdb3nsjFCvTdjug+owrCgZRbqmgmZN9qt5NWF78HgTA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I could try to reproduce the problem. I'll keep you in touch
Regards,
Fabrice
On Thu, Feb 19, 2026 at 1:14 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Feb 18, 2026 at 5:40 AM Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-02-19 08:31:45 | Re: Make copyObject work in C++ |
| Previous Message | wenhui qiu | 2026-02-19 08:19:44 | Re: [PROPOSAL] Doublewrite Buffer as an alternative torn page protection to Full Page Write |