| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Subject: | Re: walsummarizer can get stuck when switching timelines |
| Date: | 2026-07-22 14:51:41 |
| Message-ID: | CA+TgmobiOWKwec1koA6js27srZ=CuXy9OKuQ3BHgDM_GGtGfFw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 16, 2026 at 2:31 AM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
> I was wondering whether it's worth improving this. We could enable summarize_wal
> on node3 only after the WALs on the new timeline become readable on node3, which
> would eliminate the retry and reduce the test time by about 10 seconds on my
> machine. However, if the intention is to exercise the retry logic in
> WalSummarizerMain as well, the current test is fine as is. Just sharing this in
> case the test time wasn't intentional.
This is a good suggestion, thanks.
Here is v3.
--
Robert Haas
EDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Prevent-walsummarizer-from-getting-stuck-at-a-tim.patch | application/octet-stream | 17.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ants Aasma | 2026-07-22 14:52:02 | Re: [PATCH] Batched clock sweep to reduce cross-socket atomic contention |
| Previous Message | Álvaro Herrera | 2026-07-22 14:38:55 | Re: Allow pg_read_all_stats to see database size in \l+ |