| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, x4mmm(at)yandex-team(dot)ru, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: walsummarizer can get stuck when switching timelines |
| Date: | 2026-07-17 19:02:55 |
| Message-ID: | CA+TgmoZ7-CaTEfP8xN1B7ncB4r1y1FMhPtm5LdwVM3sek6wEug@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 17, 2026 at 12:22 PM Thom Brown <thom(at)linux(dot)com> wrote:
> It's erroring out, but shouldn't it check for 000000020000000000000003
> before doing so? It wasn't removed, just renamed.
Actually, neither is the case. 000000010000000000000003 was not
archived. 000000020000000000000003 is a different file with partially
identical contents. But the fact that the existing error message here
is not quite right is not a problem this patch should be trying to
solve.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-07-17 19:24:19 | Re: Report index currently being vacuumed in pg_stat_progress_vacuum |
| Previous Message | Scott Ray | 2026-07-17 18:11:54 | Re: Report oldest xmin source when autovacuum cannot remove tuples |